commonmark / commonmark/commonmark.js
Source maps
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 231
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 3
Description
See jgm/CommonMark#57, especially @zdne's comment.
Instead of starting and ending line and column for each element, we need to associate each element with a possibly non-contiguous range of positions in the source.
This is because CommonMark inline elements can be broken by indicators of block structure:
> *emphasized
> text*
Here the second > should not be considered part of the emphasized text, even though it occurs after the start of the emphasized text and before the end.
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 with the issue description and the referenced CommonMark#57 discussion, especially @zdne's comment, then trace how the parser currently associates elements with source positions. Done means elements can represent possibly non-contiguous source ranges, including the shown emphasis example where the block-structure marker is excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100