Bug using slash in string
See original GitHub issuei have a bug using a / in a string that break the syntax coloration :
let type = null
if (bill) {
type = 'Ex/ample' // here syntax isn't render correctly
} else if (vn) {
type = 'Something'
} else if (ctn) {
type = 'Something else'
} else if (imo) {
type = 'Something else'
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Potential String bug? - Scripting Support - DevForum | Roblox
I'm trying to use backwards-slashes in a string to make a windows command prompt type system, but i came across this pest of...
Read more >Backslash bug in JavaScript - Stack Overflow
If the sequence you want to match is a single backslash character followed by a quotation mark, then you need to escape the...
Read more >Using a forward slash in the search string results in error - Bugs
The request looks correctly URL-encoded. Apparently the server can't deal with the search string correctly. Chris, can you have a look? Comment ...
Read more >Can't handle file names with slashes and backslashes - PHP
If the filename contains a slash, the filename is interpreted as a directory name followd by a filename. e.g. foo/bar.
Read more >Backslash converted to forward slash when copying file:// url ...
Examples of appropriate bugs: URLs with backslash not fetched; URLs starting with a single slash turn into http:///; Cannot access authenticated FTP site....
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
When the flow syntax extension sees
type
at the beginning of the line, it assumes that it’s a type annotation. This should be an easy fix. If I don’t get to it today due to the holidays, it should be fixed by Wednesday.it’s fix with v1.0.28 👍