This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.
- I have read the contribution guidelines.
- If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
- If any large changes are made to a service, they are reflected in the respective change log.
- Title of the pull request is clear and informative.
- There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
- The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).
- Pull request includes test coverage for the included changes.
- PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.
- New cmdlets that make changes or have side effects should implement
ShouldProcessand haveSupportShouldProcess=truespecified in the cmdlet attribute. You can find more information onShouldProcesshere. - Cmdlet specifies
OutputTypeattribute if any output is produced - if the cmdlet produces no output, it should implement aPassThruparameter.
- Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
- Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
- Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.