warn about U+2028 and U+2029
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 153
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
The codepoints U+2028 and U+2029 are [not valid in JavaScript string literals](http://timelessrepo.com/json-isnt-a-javascript-subset), and any utfgrid JSON that contains them literally will not be usable with JSONP. We should note this in the spec and recommend avoiding them or encoding them as `\u2028` and `\u2029` wherever they appear in the grid strings.
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
Locate the specification section covering grid strings and JSONP, then read the surrounding guidance before making the documentation change. Document the U+2028 and U+2029 limitation and recommend avoiding them or encoding them as \u2028 and \u2029; done means the spec clearly states both recommendations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100