feat: Support for extended syntax
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 61.6k
- Forks
- 4.6k
- Avg merge
- 23h 49m
- Merged PRs (30d)
- 89
Description
Describe your feature request
I love that MarkText allows preferences toggles for pandoc syntax, it would be great to have similar toggles to enable more syntax from the full extended syntax.
What parser does MarkText use under the surface? If it's markdown.it then I know from experience (albeit with their Python package, not JS/Eltrn) that these can be turned on and off by passing booleans to the parser's constructor.
Additional context
I ran into this while trying to create a definition list, if there's any kind of priority list for which aspects of the extended syntax to implement first then count me as one vote for definition lists!
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
No file, test, or parser entry point is named in the issue; first identify which parser MarkText uses and where the existing Pandoc syntax preferences are wired. Review the full extended-syntax options, starting with definition lists, and clarify which options should be supported and independently toggled before implementation; done means the selected syntax works and its preference behaves consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100