The module standard now specifies modern PowerShell only (minimum 7.6, current + LTS; no Windows PowerShell 5.1) — see PR #61 (PowerShell/index.md).
However, the Process-PSModule framework still enforces rules that exist purely for 5.1 compatibility, notably the NoTernary framework test (documented in PowerShell/Modules/Standards.md as 'No ternary operators — maintain PowerShell 5.1 compatibility').
Task: reconcile the framework's 5.1-compat rules with the modern-only policy. Decide whether to drop NoTernary (and any other 5.1-only constraints) so modules can use 7.x language features (ternary, ??, ??=, pipeline-chain operators). This is a Process-PSModule change; update the Standards.md enforced-tests table once decided.
The module standard now specifies modern PowerShell only (minimum 7.6, current + LTS; no Windows PowerShell 5.1) — see PR #61 (
PowerShell/index.md).However, the Process-PSModule framework still enforces rules that exist purely for 5.1 compatibility, notably the
NoTernaryframework test (documented inPowerShell/Modules/Standards.mdas 'No ternary operators — maintain PowerShell 5.1 compatibility').Task: reconcile the framework's 5.1-compat rules with the modern-only policy. Decide whether to drop
NoTernary(and any other 5.1-only constraints) so modules can use 7.x language features (ternary,??,??=, pipeline-chain operators). This is a Process-PSModule change; update theStandards.mdenforced-tests table once decided.