You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Editor and Version: VS Code: 1.26.0 (with manual tweaks)
Your primary theme: Dark+
Issue Description
Presently, the documentation keyword detection/scoping/theming fails on the following items:
# .keyword doesn't detect and scope
<# .keyword doesn't detect and scope
once inside a comment block, extra # separated by spaces allows the keyword to detect, but Get-Help doesn't seem to permit this.
once inside a comment block, extra characters after a keyword that doesn't accept arguments allows the keyword to detect, but Get-Help doesn't seem to permit this.
Screenshots
(Showing modified sample from file attached to #134)
Expected Behavior
Expected to match Get-Help's acceptance. However, that's much more difficult. Get-Help also accepts:
<##># <additional #s> .keyword
does not accept .keyword if the containing comment doesn't otherwise start at the beginning of a line
and has limited acceptance of consecutively spaced and required placement, that probably only script analysis can accurately report on.
Possible Fix
I think two changes could fix the easiest problems.
Change the match for 'commentEmbeddedDocs' to
(#\1 match)
Uh oh!
There was an error while loading. Please reload this page.
Environment
Issue Description
Presently, the documentation keyword detection/scoping/theming fails on the following items:
# .keyword
doesn't detect and scope<# .keyword
doesn't detect and scope#
separated by spaces allows the keyword to detect, but Get-Help doesn't seem to permit this.Screenshots
(Showing modified sample from file attached to #134)
Expected Behavior
Expected to match Get-Help's acceptance. However, that's much more difficult. Get-Help also accepts:
<#
#>
#
<additional#
s>.keyword
.keyword
if the containing comment doesn't otherwise start at the beginning of a linePossible Fix
I think two changes could fix the easiest problems.
(#\1 match)
and change the capture from "0" to "1".
With the changes applied, this is the result:
(not necessary valid, I know)
The text was updated successfully, but these errors were encountered: