Merged
requested to merge github/fork/SimeonGerginov/topic/sgerginov/powershell-example-structure into master
Created by: SimeonGerginov
-
Integer
default value in the examples is changed from123
and789
to0
. -
String
default value is now constructed from the name of theparameter/property
and the prefixMy
. Previously the suffixexample
was part of the value. -
Enum
examples are now generated using one of the allowed values of theEnum
instead of using theInitialize-*
cmdlets as before. -
Arrays
with one element result in the value directly instead of adding the@()
syntax. -
Maps
are now fully supported using thehashtable
syntax inPowerShell
. -
Models
are extracted and generated in the correct order instead of nesting them on a single line when invoking the cmdlet. - The verb that is used in the examples for the
Models
cmdlets can now be specified through an additional property. The default value remainsInitialize
. -
Classname
is used instead ofName
in theModels
cmdlets initialization. This can be controlled through an additional boolean property which specifies whether to useClassname
instead ofName
. - The
PowerShell Samples
are updated to reflect the latest example structure. - The docs template for the APIs is modified as well to reflect the latest example structure.
- The documentation for
PowerShell
is changed to reflect the new additional properties.
Closes #9826 (closed) @wing328
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: ./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh
./bin/generate-samples.sh bin/configs/java*
. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master
,5.1.x
,6.0.x
-
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.