Open
Conversation
Having a space after commas is a rather common style so make it configurable. Note a spurious [<CommonParameters>] in the README has been removed.
This makes it easy to tweak 'add space after' behavior.
This makes the spacing in all groups (arrays, hashtables, script blocks, ...)
the same which is more consistent overall: when removing spaces in arrays
like @(1) it makes sense doing that also for e.g. @{a = 1}.
Default is still $false for backwards compatibility.
ghost
approved these changes
May 26, 2022
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.
We use a slightly different style for formatting PS code but still would like to use this formatter so here's a bunch of changes which gets it to the style we use. Summary:
@()and@{}for instance are formatted the same instead of the latter having spaces but not the former)$x | %{...}instead of$x | % {}All of these are optional so existing users shouldn't be affected, I think.
For reference, example of how we use this now: