Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect color coding #164

Closed
gbritton1 opened this issue Apr 23, 2019 · 2 comments · Fixed by #165
Closed

Incorrect color coding #164

gbritton1 opened this issue Apr 23, 2019 · 2 comments · Fixed by #165

Comments

@gbritton1
Copy link

2019-04-23_15-21-26

Issue Type: Bug

Enter an interpolated string like

"git:https//$($env:UserName)@bitbucket.tds.td.com"

Expect that only the $(...) expression is blue, but i see the @bitbucket... also in blue, expect that to be in light brown like the first part of the string

Extension version: 1.12.1
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.16299

System Info
Item Value
CPUs Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1896)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 31.84GB (15.74GB free)
Process Argv
Screen Reader no
VM 0%
@rjmholt
Copy link

rjmholt commented Apr 23, 2019

Thanks for reporting this issue @gbritton1. The grammar for PowerShell syntax highlighting is maintained in the Editor Syntax repo

@SteveL-MSFT SteveL-MSFT transferred this issue from PowerShell/vscode-powershell Apr 23, 2019
@msftrncs
Copy link
Contributor

This has been reported before as #149, and mentioned in #137 (regarding rewriting the variable logic), if not earlier.

PR #155 and #156 do not exhibit this error.

@omniomi, I never noticed this before, I long ago cleaned this up while experimenting, but #doubleQuotedString includes both #variableNoProperty and #variable. Also, #variableNoProperty possesses a match pattern that would include some variations of @scope:variable.

I will try to shortly post a PR for these apparent mistakes/oversights.

msftrncs added a commit to msftrncs/EditorSyntax that referenced this issue Apr 24, 2019
remove #variable from #doubleQuotedString, remove @ from #variableNoProperty
TylerLeonhardt pushed a commit that referenced this issue Apr 26, 2019
* fixes #149, #164
remove #variable from #doubleQuotedString, remove @ from #variableNoProperty

* add tests: no @splats in double quoted strings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants