Incomplete unicode escape in template literal gets parsed without errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 773
- PR merge metrics
- No merged PRs in 30d
Description
Hello
Is it intentional that incomplete unicode escape sequences in template literals cause no errors? because things like \u get parsed without errors:
var l = require('esprima')
console.log(l. parse('`\\u`').body[0].expression)
Furthermore, I came across a test case, in which this very idiosyncrasy has been put to actual test (and looks to have passed it).
I'm not sure whether this kind of behavior has been mentioned in the spec; if it is, then I'd be glad should you help me find it; but in case it's not, it would be great to have it expressly mentioned (somewhere.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the l.parse('\\u') entry point and read test/fixtures/ES6/template-literals/literal-escape-sequences.source.js. Check the applicable ECMAScript rules to determine whether the incomplete escape should be accepted. Done means the behavior and expected outcome are established, with the relevant test or documentation reflecting that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100