Change v2 schema for parameter. #622
Conversation
Parameter now contains a collection of parameter sets which will enable tracking a number of attributes on a parameter _and_ parameterset basis. This is because a parameter may be position in one parameter set but not positional in another parameter set.
| }, | ||
| "applicable": { | ||
| "applicable": { // ???? |
There was a problem hiding this comment.
This is an Office only thing.. @theJasonHelmick was going to reach out and verify if this is still something they still need.
There was a problem hiding this comment.
This applicable attribute might need to be moved into parameterset.parameter
There was a problem hiding this comment.
i wasn't sure what it means (thus the ???) - there doesn't seem to be an actual parameter attribute property of this name
There was a problem hiding this comment.
It is used by the Merge-Markdown cmdlet.
| "type": "string" | ||
| }, | ||
| "position": { | ||
| "type": "string" |
There was a problem hiding this comment.
Can this now be an int?
There was a problem hiding this comment.
i think it can, but i've not gone through the current examples to see if it's "named" anywhere
There was a problem hiding this comment.
Maybe. PowerShell shows named parameters as [int]::MinValue. But we show it as Named in the markdown yaml block. So it is a data vs. rendering question.
| @@ -194,7 +217,7 @@ | |||
| "minItems": 1, | |||
| "type": "array" | |||
| }, | |||
| "commonParameters": { | |||
| "commonParameters": { // This implies has cmdlet binding | |||
There was a problem hiding this comment.
This is supposed to be optional. Not all commands implement cmdlet binding.
Parameter now contains a collection of parameter sets which will enable tracking a number of attributes on a parameter and parameterset basis. This is because a parameter may be position in one parameter set but not positional in another parameter set.
PR Summary
PR Context