Improve syntax coloring definition to meet the standards of PowerShell ISE, Visual Studio

[v-pavanp]

I compare VSCode coloring with Visual studio with different themes and observed that the cmdlet, parameter name and values are not following correct pattern.
Actual:

1. With Light (Visual Studio) and Dark+ (Default Dark) themes the PS comdlet , parameter and parameter value are displaying in the same color.

1. When multiple parameters are provide with the command then they are displaying in the different color.
   Exp: In the below screenshot you can see -class and -computer is displaying in different color and Win32_OperatingSystem and localhost are displaying in different color.
   
   Expected: Cmdlet, parameter and value should be display in three different colors and should be consistent in the script file same like visual studio.
   

[daviwil]

Hey Pavan, the problems you see with VS Code's syntax highlighting for PowerShell come from the TextMate syntax definition we borrowed from Sublime Text which is based purely on regular expressions. We won't be able to keep 100% consistency with Visual Studio and the PowerShell ISE because VS Code does not allow us to implement a custom classifier based on the PowerShell parser.

That said, we need to improve the syntax definition to be more consistent with what users expect. We've got a plan to take over maintenance of the TextMate syntax definition that we use so that we can improve the quality of its colorization, it just may take a little while before we get to it.

[gravejester]

I'd love to help out with this one @daviwil.

[daviwil]

That'd be fantastic! Would love some help on that. I need to create a GitHub repo for the common syntax coloring definition used across VS Code, Sublime Text and Atom. I'll get that started today.

[gravejester]

Nice, let me know when you have it set up and I'll start taking a look at it. :)

[vors]

Excellent, lets do it!
For sublime side of things see SublimeText/PowerShell#148