adding update capabilities for classification nodes by a11smiles · Pull Request #470 · MethodsAndPractices/vsteam

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles · 2022-06-28T21:41:00Z

PR Summary

Added Update-VSTeamArea and Update-VSTeamIteration wrappers and their base function Update-VSTeamClassificationNodes to allow updates to classification nodes.
Updated StartTime and FinishTime to be nullable for iterations, which includes the base classification nodes functions.
Updated the ClassificationNode object to provide a direct reference to an iteration's start and finish date, if provided, rather than being required to access them through the InternalObject.
Small updates to typos in the documentation.

For the second bullet, consider the following scenario:

In a situation where I'm syncing two projects (e.g. copying iterations from one to another), the current implementation would require me to write the following if-else statement to check if dates are provided because it doesn't allow for a nullable DateTime.

if ($null-eq$Node.InternalObject.Attributes.StartDate) {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path
} else {
Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate
}

Not allowing a nullable DateTime is okay if the node is net new. However, I have the write this if-else for pre-existing nodes when attempting to simply copy them.

[Add|Update]-VSTeamIteration

Params changed to the following:

[Parameter(Mandatory=$false)]
[Nullable[datetime]] $StartDate,
[Parameter(Mandatory=$false)]
[Nullable[datetime]] $FinishDate,

This also removes the need for these if statements. (Also, AzDO requires that if one date is set, the other MUST also be set. It won't allow a StartDate and not a FinishDate, and vice versa.)

if ($StartDate) {
$params.StartDate=$StartDate
}
if ($FinishDate) {
$params.FinishDate=$FinishDate
}

By making the above changes, I no longer need my original if-else statement. I can simply write the following one line and the null values are accepted.

Add-VSTeamIteration-ProjectName $DestinationProject-Name $Node.Name-Path $Path-StartDate $Node.InternalObject.Attributes.StartDate-FinishDate $Node.InternalObject.Attributes.FinishDate

PR Checklist

a11smiles · 2022-07-01T22:29:24Z

@SebastianSchuetze can you run the workflows please? I had a mistype in my unit tests. Thanks!

SebastianSchuetze · 2022-07-02T19:02:13Z

looks like you have green lights. I will review in the next few days.

SebastianSchuetze

Please check the comments. Nothing serious. Otherwise I will approve as soon as I understand or changes are made. :-)

SebastianSchuetze

Sorry forgot to save my other suggestions @a11smiles :-)

SebastianSchuetze · 2022-07-25T05:09:47Z

@a11smiles anything I can help with to get this PR finished?

Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

a11smiles · 2022-08-03T01:37:33Z

I wasn't sure how particular you guys were with 'return' vs. 'update'. Thanks for making the changes.

SebastianSchuetze

All good now, thanks!

a11smiles added 6 commits June 28, 2022 16:42

adding update capabilities for classification nodes
b970f88

updating changelog
ad86de4

update version number
dd4d1b3

adding ShouldProcess support
233df9f

fixed typo
c2a3018

forgot the stupid backticks :)
bf47b37

SebastianSchuetze requested review from DarqueWarrior and SebastianSchuetze July 2, 2022 19:02

SebastianSchuetze reviewed Jul 17, 2022
View reviewed changes

Comment threadSource/Classes/Provider/ClassificationNode.cs

SebastianSchuetze suggested changes Jul 17, 2022
View reviewed changes

a11smilesand others added 6 commits August 2, 2022 21:36

Update Tests/function/tests/Update-VSTeamIteration.Tests.ps1
cfaadc3
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

Update Tests/function/tests/Update-VSTeamIteration.Tests.ps1
dde2fa4
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

Update Tests/function/tests/Update-VSTeamClassificationNode.Tests.ps1
03857f6
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

Update Tests/function/tests/Update-VSTeamClassificationNode.Tests.ps1
42e0e87
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

Update Tests/function/tests/Update-VSTeamArea.Tests.ps1
83e617a
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

Update Tests/function/tests/Update-VSTeamArea.Tests.ps1
33209e5
Co-authored-by: Sebastian Schütze <sebastian.schuetze@razorspoint.com>

SebastianSchuetze enabled auto-merge (squash) August 5, 2022 15:07

SebastianSchuetze approved these changes Aug 5, 2022
View reviewed changes

SebastianSchuetze merged commit 33c5f0c into MethodsAndPractices:trunkAug 5, 2022