Decide on scope names for all language constructs

Review the scope-name table and the refactored language file mentioned in the issue, then compare the proposed names with the documented VS Code theme scopes. The work is done when the scope naming discussion reaches an agreed convention for the listed PowerShell constructs and the table reflects that decision.

I'd like to have a discussion where we decide on the "correct" scope names for all PowerShell language constructs. This will mean much less work when doing updates to the tmLanguage file in the future, as the scopes (as well as the color(!) of each) are checked by a Travis CI build job on the vscode repo.

General

• All scope names should end in .powershell

As we decide, we can fill out this table:

I have started by filling out the scope names as I have used them in my refactored language file.

About scopes and highlighting

If, in the theme, there are colorization rules only for the scope constant.operator, both constant.operator and constant.operator.range will be colorized the same.

If there isn't any colorization rules for a scope, it will be colorized with the "root" color of the current scope. Meaning if the word 'test' only belong to the source scope (or have a scope name that is not defined in the current theme), it will be colorized with the default background color. If the word 'test' is found inside another scope, for instance a string, it will be colorized with the color for the string scope.

Colorization rules may differ between editors. For instance the background parameter. This is supported on Sublime Text, but not in VSCode.

A matched set of characters can be (and more often than not are) assigned multiple scopes. So for example the word variable in function MyFunction {"this is $("a $variable")"} have the following scopes: source, string.quoted.double, meta.subexpression, string.quoted.double and lastly variable.other.readwrite. Only the last one is used for colorization.

About the default themes in VSCode

There are five themes that are defined as default themes in Visual Studio Code:

• dark_plus "Dark+"
• dark_vs "Dark Visual Studio"
• hc_black "Dark Visual Studio"
• light_plus "Light+"
• light_vs "Light Visual Studio"

The themes supports nesting, and:

• Light+ includes light_vs (Light Visual Studio)
• Dark+ includes dark_vs (Dark Visual Studio)

The following scopes are defined in the plus-themes:

• meta.type.name, meta.return.type, meta.return-type, meta.cast, meta.type.annotation, support.type, entity.name.class, entity.name.type, storage.type.cs, storage.type.java
• entity.name.function, entity.name.method
• keyword.control
• meta.parameter.type.variable, variable.parameter, variable, variable.name

The following scopes are defined in the "old" default themes:

• emphasis
• strong
• header
• comment
• constant.language
• constant.numeric
• constant.regexp
• constant.rgb-value
• entity.name.tag
• entity.name.selector
• entity.other.attribute-name
• entity.other.attribute-name.css
• invalid
• markup.underline
• markup.bold
• markup.heading
• markup.italic
• markup.inserted
• markup.deleted
• markup.changed
• meta.selector
• meta.tag
• meta.preprocessor
• meta.preprocessor.string
• meta.preprocessor.numeric
• meta.structure.dictionary.key.python
• storage
• storage.type
• storage.modifier
• string
• string.xml, string.jade, string.yaml, string.html
• string.regexp
• support.property-value
• support.type.property-name.css, support.type.property-name.less, support.type.property-name.sass
• support.type.property-name
• keyword
• keyword.control
• keyword.operator
• keyword.operator.new
• keyword.other.unit
• keyword.control.less
• metatag.php
• support.function.git-rebase
• constant.sha.git-rebase
• storage.modifier.import.java, storage.modifier.package.java

Scope names on the same line, means they are defined in the same colorization rule.