Optional raw identifiers
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 773
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
esprima.parse('var \u00e0;')
Expected output
{
"type": "Program",
"body": [
{
"type": "ExpressionStatement",
"expression": {
"type": "Identifier",
"name": "\u00e0"
}
}
],
"sourceType": "script"
}
Actual output
{
"type": "Program",
"body": [
{
"type": "ExpressionStatement",
"expression": {
"type": "Identifier",
"name": "à"
}
}
],
"sourceType": "script"
}
I didn't expect identifiers in unicode format to be transformed, which is okay of course, I would like to ask if an option to keep Identifiers and function names unencoded can be added.
Thanks!
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 running the reported esprima.parse('var à;') reproduction and trace how identifier names are represented in the parser output. Define the option's behavior for identifiers and function names, then add coverage showing raw spelling is preserved when enabled without changing the default output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100