Issue with string that contains []
See original GitHub issueif you have a string like:
"policyAssignmentDisplayName": "[Preview]: Audit VMs with insecure password security settings",
You will get error message: Unrecognized function name ‘Preview’.
The usage of [] in strings is documented here: https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-expressions#escape-characters
and should not result in error.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Issue with using the String.Contains() - vb.net - Stack Overflow
I've tried 2 different methods, the first just being a basic String.Contains() command, which I've set out as such:
Read more >String.prototype.includes() - JavaScript - MDN Web Docs
The includes() method performs a case-sensitive search to determine whether one string may be found within another string, returning true or ...
Read more >JQL search for string that contains a dash "-"
I need to be able to search a paragraph text field in Jira issues for strings that contain a "-" character and a...
Read more >String & Binary Data Types - Snowflake Documentation
This topic describes the string/text data types, including binary strings, supported in Snowflake, ... VARCHAR holds Unicode UTF-8 characters.
Read more >String - LeetCode
# Title Acceptance Difficulty
3 Longest Substring Without Repeating Characters 33.8% Medium
5 Longest Palindromic Substring 32.4% Medium
6 Zigzag Conversion 43.3% Medium
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@slavizh Thanks Stan, I’ll go ahead and get this fixed.
@slavizh Closing this in favor of #250. The tricky part is not messing up the experience of users that are in the middle of editing strings that may or may not be completed. Have a couple of possible solutions that we’ll try internally first, so this won’t make it into 0.15.1.