⚙️ [Maintenance]: Module source tests align with latest PowerShell LTS - #419
Merged
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Module source validation no longer carries the obsolete PowerShell 5.1 ternary compatibility rule. PSModule modules targeting the latest PowerShell LTS can use ternary operators without an outdated framework restriction.
Changed: Ternary operators are allowed
The source-code test suite no longer checks for or supports bypassing the retired
NoTernaryrule. No other source-code rules change.Technical Details
NoTernaryPester test and its#SkipTest:NoTernary:handling from.github/actions/Test-PSModule/src/tests/SourceCode/PSModule/PSModule.Tests.ps1.