Whilst developing a Powershell module that required custom interfaces, we discovered that we had to maintain back-compatibility with Powershell v5.1 (Desktop) and then that we had used features that were not supported in this old version of Powershell. Fortunately PSScriptAnalyzer (Invoke-ScriptAnalyzer) can be used to check compliance with different levels of Powershell as describe in the ref below.
We propose that such checking be added to the autorest generation process such that developers can choose to enable such checking and ensure that future changes do not break such requirements.
https://github.com/Azure/azure-powershell/pull/26540 has a proposed tool that can be used to manually perform such a check based on configuration in the autorestREADME.md file. This might be used as the basis for the proposed feature.
vidai-msft
commented
2 weeks ago
Description of the new feature
Whilst developing a Powershell module that required custom interfaces, we discovered that we had to maintain back-compatibility with Powershell v5.1 (Desktop) and then that we had used features that were not supported in this old version of Powershell. Fortunately
PSScriptAnalyzer(Invoke-ScriptAnalyzer) can be used to check compliance with different levels of Powershell as describe in the ref below.We propose that such checking be added to the autorest generation process such that developers can choose to enable such checking and ensure that future changes do not break such requirements.
Proposed implementation details (optional)
https://github.com/Azure/azure-powershell/pull/26540 has a proposed tool that can be used to manually perform such a check based on configuration in the
autorestREADME.mdfile. This might be used as the basis for the proposed feature.