commonmark / commonmark/commonmark-java
Unable to override default delimiter processors
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I wish to override the default delimiter processors the sake of better supporting Discord's markdown quirks. However, I am left unable to override the default options without an exception being thrown due to conflicting characters.
Describe the solution you'd like
I would like to be able to override the two default delimiter processors with my own implementations of the two somehow within the Parser builder.
Describe alternatives you've considered
The current solution for this is to copy the InlineParserImpl class and make your modifications to it, which is definitely not ideal.
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 Parser builder and InlineParserImpl, especially how the two default delimiter processors are registered and how conflicting characters are validated. Trace the existing option-registration path and determine how custom implementations could replace those defaults without the conflict exception. Done means the builder accepts both overrides and Discord-style delimiter behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100