Account for escaped quotes and backslashes in strings
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 132
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Right now, the tokeniser doesn’t properly account for escaped quotes in strings. In particular, it can’t handle more than one backslash immediately preceding a quote. In other cases, the output may not always match the input. ToDo fix.
Contributor guide
No contributing guide indexed for this repository
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 locating the tokenizer entry point and reproduce strings containing escaped quotes and multiple backslashes immediately before a quote. Compare the tokenizer output with the original input; done means these cases tokenize correctly without changing other string contents.
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
- Mostly clear
- Newbie friendliness
- 45/100