PR Summary

Flag the switch statement condition clause default token as a keyword
token to facilitate (PSReadLine) highlighting it as a keyword. Closes #10470.

This change is to treat the default clause keyword as a full keyword token, and as such token based highlighters will see it as a keyword.

PR Context

Flagging the default condition clause token of the switch statement as a keyword will facilitate highlighting of the keyword to better contrast against other bareword string literal conditions.

A simple (partial) example:

# return simple element value (need to check for Boolean datatype, and process value accordingly)
switch ($node.Name) {
    true { $true; continue } # return a Boolean TRUE value
    false { $false; continue } # return a Boolean FALSE value
    default { $node.Value } # return the element value
}

Highlighting of the default keyword in the above example makes it easier to distinguish the special condition clause from the other bareword conditions.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).