-
Notifications
You must be signed in to change notification settings - Fork 50
Closing round bracket breaks syntax highlighting on ValidatePattern parameter attribute #74
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
Comments
From @tonylea on February 21, 2017 13:26 I've also noticed this issue. Using:
Validate pattern am using: |
From @cantrellj on February 22, 2018 17:56 Appears to happen in ValidateScript also System Details
|
From @rkeithhill on February 23, 2018 3:34 Syntax highlighting is being managed out of the https://GitHub.com/powershell/editorsyntax project. @tylerl0706 Can you move this issue over to that repo? |
From @gazm81 on April 6, 2018 0:6 This is still an issue in VS code 1.21.1 with PowerShell plugin 1.60. |
This is the same as issue #75, I found a fix and will submit a PR after more testing. |
Nice one, thanks @omniomi ! |
@omniomi is the man 🎉 💪 |
Fixed by #94 |
From @jlucktay on December 4, 2016 16:5
System Details
$PSVersionTable
:Issue Description
I am experiencing a problem with syntax highlighting inside a ValidatePattern attribute on a parameter.
The highlighting seems to break if I make use of a closing round bracket
)
inside the validation pattern.In that part of the pattern, I want the URL to optionally have
videos/
in it.Here is the code from the screenshots, to save from having to type it out when reproducing:
Please see the screenshots below.
The function itself executes fine and works absolutely as expected and desired with the round bracket in place, so it's just the syntax highlighter getting confused about the round bracket inside the pattern string.
Attached Logs
OK without the round bracket
Not OK with the round bracket
Copied from original issue: PowerShell/vscode-powershell#357
The text was updated successfully, but these errors were encountered: