Fix parse error in Windows PowerShell#136
Merged
Jaykul merged 1 commit intoPoshCode:mainfrom Apr 12, 2025
Merged
Conversation
This was referenced Feb 28, 2025
Closed
|
@Jaykul, any chance you can get this merged? Anything testing with PS5 is failing currently. |
Member
|
Holy cow, I thought we already merged this ... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
This will fix issue #135.
In Windows PowerShell this will not work:
but this will:
By moving the Version property at the end there is no parse error.
This error does not occur on PowerShell 7.x. It handles if-blocks in hashtables better apparently.