escaping literal quotes challenge does not validate syntax accurately
See original GitHub issueChallenge Escaping Literal Quotes in Strings has an issue.
User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
.
Please describe how to reproduce this issue, and include links to screenshots if possible.
while attempting to complete challenge escaping literal quotes. Validation fails on accurate syntax. i am sure that my declaration is correct.
My code:
//var myStr = "I am a \"double quoted\" string inside \"double quotes\"";
var myStr = "I am a \"double quoted\" string inside \"double quotes\"";
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
I need help with escaping literal quotes - JavaScript
You don't need to escape single-quotes in a double-quote string. Nor vice versa. You just need to escape the same quote style as...
Read more >How to escape single quotes within single quoted strings
There is no way to escape single quotes or anything else within single quotes. The following is, perhaps surprisingly, a complete command: $...
Read more >When to escape characters - Splunk Documentation
Characters and escape sequences that must be escaped To escape a double quotation mark ( " ), use the sequence \" to search...
Read more >How to Handle the Unclosed String Literal Error in Java - Rollbar
a double quote is part of the string literal itself but is not escaped properly. Unclosed String Literal Error Examples. Missing double quotes...
Read more >Escaping Literal Quotes in Strings, freeCodeCamp Basic ...
In this challenge we learn how to add multiple double or single quotes inside of our string by using the backslash escape character...
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 FreeTop 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
Top GitHub Comments
I got mine to work by putting the period before the last quotation mark. Hope this helps.
Closing this as it appears to be fixed in beta and locally.