[PowerShell][BUG] Fix issue #18427 - Array context not maintained when converting a parameter to JSON #19262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix an issue due to PowerShell pipeline behaviour: when an array of a single element is passed into a pipeline the array context is not preserved.
When the result of the pipeline is the generation of the JSON body of an API request, it causes the server side to receive an unexpected type when an array of a single element is passed to the PowerShell client function. See Issue #18427
The fix forces the array context when the parameter corresponding to the variable
$LocalVarBodyParameter
is an array type.PSPetstore endpoints that require an array type are not implemented on the server side, so the fix has been tested on the Connectwise PSA API.
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming 7.6.0 minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)