(PowerShell) Specific elements not being identified for highlighting

Describe the issue

Syntax highlighting isn’t working for some elements of PowerShell. I think the PowerShell language grammar to identify certain elements needs to be updated.

1. The entire line after a # sign is commented even if there no space after #
2. The Noun part of the cmdlet isn’t highlighted
3. The parameter name isn’t highlighted
4. PowerShell parameter arguments don’t need to be in quotes unless there is a space in between

**Are you using highlight or highlightAuto? highlight

…

Sample Code to Reproduce

<link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.3.1/build/styles/atom-one-dark.min.css">
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.3.1/build/highlight.min.js"></script>
<script>hljs.highlightAll();</script>

<pre><code class="pwsh">
    #Locate SQL image
    Get-AzVMImagePublisher -Location 'southcentralus'|? PublisherName -Like *sql*
    Get-AzVMImageOffer -Location southcentralus -PublisherName MicrosoftSQLServer
</code></pre>   

CodePen link to reproduce issue: https://codepen.io/ayanmullick/pen/YzrPobY

Expected behavior

Screenshot:

Library: This screenshot is from PowerShell ISE. One could export the theme XML from Tools-Options-Manage themes-Export One gets similar highlighting experience on Discord too.

Additional context : NA

[joshgoebel]

-Like is a comparison operator

Then I’d say operator is correct and we just need to wait for themes to catch up - and those who truly care right now need to tweak their own CSS to better support operators. I’d also say base16 themes may not be best-suited to grammars that use “keyword like” operators, like Powershell.

[Ayanmullick]

Operator highlighting is working fine with the atom-one-dark-reasonable theme. 😄