-
Notifications
You must be signed in to change notification settings - Fork 81
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
Does not correctly handle when a string starts with a bracket but does not end with a bracket #250
Milestone
Comments
Example template that shows the rules:
Output:
|
sbuttar
pushed a commit
to sbuttar/vscode-azurearmtools
that referenced
this issue
Jun 5, 2019
…cket but does not end with bracket
StephenWeatherford
added a commit
that referenced
this issue
Jul 18, 2019
* Fix #250, strings vs expressions boundary cases * Simplify output of colorization tests * lint?
StephenWeatherford
changed the title
Does not correctly handle the case when a string starts with a bracket but does not end with a bracket
Does not correctly handle colorization when a string starts with a bracket but does not end with a bracket
Sep 9, 2019
StephenWeatherford
added a commit
that referenced
this issue
Sep 17, 2019
* Use standalone language server * fix * work * suites work * suites work * work * work * Test format range * lint * work * format range suites * cleanup * work * Work on Mac * schema validation tests * fix suites * fixes * fix tree tests * Fix colorization suites * Fix more tests * work on functional tests * fix launch.json * Working on expressions functional tests * Expression suites * Expression suites * lint * Change diagnostics source * Fix lang server path * Fix suites * arrow functions * Simplify output of colorization tests * fix colorization results * orphaned files * Fix #250, strings vs expressions boundary cases * Fix suite * Fix suite * fix suite * Increase timeout again work * fix * Update ui * lint * Fix path check * PR fix * Disable lang server tests for now * Lang conf file must be copied to dist (#276) * Lang conf file must be copied to dist * PR fix * Acquire .dotnet core and search further in file for schema * Fix build, suites * Improve language server error handling (#282) * Always validate file if langid=ARM (#285) * Always validate file if langid=ARM * refactor * Show warnings about --wait-for-debugger and custom lang serve path (#286) * Clarify licensing for public repo, update version/readme/changelog for 0.7.0 (#283) * Remove EULA (handled by LICENSE.md) * Clarify licensing in README.md * Bump version, update changelog/readme * Additional changes * grammar * Acquire language server binaries during build (#289) * Acquire language server binaries during build * Update to get threading fix * PR fix * comment * Fixes * IMprove message * Improve message
Mistakingly closed |
StephenWeatherford
changed the title
Does not correctly handle colorization when a string starts with a bracket but does not end with a bracket
Does not correctly handle when a string starts with a bracket but does not end with a bracket
Apr 24, 2020
Decision:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authoring-templates#syntax:
But it turns out you only need the [[ if your string starts with a bracket and ends with a bracket. I.e.:
"value": "[ChefInSpec]InstalledApplicationLinuxResource1;AttributesYmlContent"
is perfectly valid and is interpreted as a string, since it does not end with a bracket.
The text was updated successfully, but these errors were encountered: