Carl Morris

Looking at things closer, its looking like `parameter` is preferred to be a `variable` sub-scope instead of under `entity`. The sublime scope recommendations lists `variable.parameter`. However, a lot of themes...

@MartinGC94, thanks for the feedback, and sorry for the very long delay. Myself, I prefer if all commands or functions scope the same, unless they are truly language standard (built-in)...

Honestly the approved verb command scoping is carried over from the current release. There are two different scopes at play here for commands: - support.function - entity.name.function While `entity.name.function` isn't...

@JustinGrote, in PowerShell, functions are really static methods (which also get the scope `entity.name.function`), not types, so `entity.name.type` would not be the right choice. The name of a PowerShell class...

There is no reason to continue to support `storage.type` for keywords. Sublime's recommendation could really be improved by putting that reference in the `keyword` section. The preferred scope should be...

@cblackuk, The way the grammar works now is actually the more correct scoping that's accepted by other languages as well. A theme can better support the original coloring if that...

FYI, this is the same as #150.

@cblackuk, if you were to add the following to your settings file, you could restore what you originally experienced. (I might not have the right theme or the right color,...

A reference, the original post's code via PR #156 and the theme mentioned above:  The final properties do stand out, but if there had been others chained, they would...

That reminds me, I need to spend a little time with ISE. Ohh… ISE only colors the variable... Whether fortunate or not, I didn't start using PowerShell until I ran...