"Continue" is highlighted as a statement/keyword when used as a parameter value

[Makumasa]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Steps to reproduce

1. Create a new file in Visual Studio Code and select PowerShell as the language.
2. Call a function/cmdlet where one of the parameter values is a keyword, e.g. "Continue".

Expected behavior

Continue is highlighted in white, like other parameter values.

Actual behavior

Continue is highlighted in purple, likely meaning it is being recognized as the continue keyword.

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.6.1
PSEdition                      Core
GitCommitId                    7.6.1
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

Version used in Visual Studio Code 1.117.0

Visuals

No response

[andyleejordan]

Maybe due to #223 @o-l-a-v can you take a look?

[RedCMD]

@andyleejordan the PowerShell grammar currently doesn't explicitly support command arguments

EditorSyntax/PowerShellSyntax.tmLanguage

Lines 525 to 570 in 23eed76

	<key>commands</key>
	<dict>
	<key>patterns</key>
	<array>
	<dict>
	<key>comment</key>
	<string>Verb-Noun pattern:</string>
	<key>match</key>
	<string>(?:(\p{L}|\d|_|-|\\|\:)*\\)?\b(?i:Add|Approve|Assert|Backup|Block|Build|Checkpoint|Clear|Close|Compare|Complete|Compress|Confirm|Connect|Convert|ConvertFrom|ConvertTo|Copy|Debug|Deny|Deploy|Disable|Disconnect|Dismount|Edit|Enable|Enter|Exit|Expand|Export|Find|Format|Get|Grant|Group|Hide|Import|Initialize|Install|Invoke|Join|Limit|Lock|Measure|Merge|Mount|Move|New|Open|Optimize|Out|Ping|Pop|Protect|Publish|Push|Read|Receive|Redo|Register|Remove|Rename|Repair|Request|Reset|Resize|Resolve|Restart|Restore|Resume|Revoke|Save|Search|Select|Send|Set|Show|Skip|Split|Start|Step|Stop|Submit|Suspend|Switch|Sync|Test|Trace|Unblock|Undo|Uninstall|Unlock|Unprotect|Unpublish|Unregister|Update|Use|Wait|Watch|Write)\-.+?(?:\.(?i:exe|cmd|bat|ps1))?\b</string>
	<key>name</key>
	<string>support.function.powershell</string>
	</dict>
	<dict>
	<key>comment</key>
	<string>Builtin cmdlets with reserved verbs</string>
	<key>match</key>
	<string>(?&lt;!\w)(?i:foreach-object)(?!\w)</string>
	<key>name</key>
	<string>support.function.powershell</string>
	</dict>
	<dict>
	<key>comment</key>
	<string>Builtin cmdlets with reserved verbs</string>
	<key>match</key>
	<string>(?&lt;!\w)(?i:where-object)(?!\w)</string>
	<key>name</key>
	<string>support.function.powershell</string>
	</dict>
	<dict>
	<key>comment</key>
	<string>Builtin cmdlets with reserved verbs</string>
	<key>match</key>
	<string>(?&lt;!\w)(?i:sort-object)(?!\w)</string>
	<key>name</key>
	<string>support.function.powershell</string>
	</dict>
	<dict>
	<key>comment</key>
	<string>Builtin cmdlets with reserved verbs</string>
	<key>match</key>
	<string>(?&lt;!\w)(?i:tee-object)(?!\w)</string>
	<key>name</key>
	<string>support.function.powershell</string>
	</dict>
	</array>
	</dict>

---

something like this could work
(I'm not sure how restrictive calling commands are)