powershell "-xxx" operators broken by formatting. how to fix?

[LeeDailey]

howdy TheColorRed,

powershell uses a large number of operators that are made up of a dash and then two or more letters. it also uses the standard increment/decrement shorthand "++" and variants. can your extension be configured handle things like the following? and if so, how?

-and -eq -or -neq -contains

right now, the format command results in those being broken into ...

- and - eq - or - neq - contains

that breaks the code, obviously. [grin]

please, can you help?

take care,
lee

[TheColorRed]

Currently it doesn't support that.

I am not sure how I should tell the extension that - should be used as part of a math equation or if it should be used as part of a string...

[LeeDailey]

howdy TheColorRed,

i suspected that would be the case. [sigh ...] i was hoping there might be a way to tell VSCode to ignore the - when associated with a list of operators.

thank you for the feedback. i will try one of the external formatters next ... [grin]

take care,
lee

[sheldonhull]

I've had an issue with the -argument values getting spaces force, so my Cmdlet calls are breaking as well.

Test-Module -value "test" -value2 "test2"
turns into
Test-Module - value "test" - value2 "test2"

I've verified I have no other format extensions installed besides "Visual Studio Code Format". When I disable the extension it fixes the problem and allows the powershell formatter to run.

Putting powershell into the disabled category disables all formatting from running.

Maybe there would be a way to bypass your implementation for the files and allow the native format options to run instead of you having to handle powershell's logic?

I also tried implementing a language override under the options. Perhaps that would be a nice solution. For example

    "language": {
            "PowerShell": {  ## OVERRIDE SPECIFIC LANGUAGE
                ".": {
                    "before": 0,
                    "after": 0
                }
            },
          "*":   ### THIS COULD BE ALL REMAINING CAN APPLY THIS LOGIC 
              ".": {
                    "before": 1,
                    "after": 1
                }
  }

What do you think?

Thanks for this cool project!