Created a custom InlineParser but it seems other parsers are not processing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.3k
- Forks
- 510
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 5
Description
I'm in the process of writing a custom parser and renderer for custom Alert blocks and I sort of have it working using InlineParser and HtmlObjectRenderer.
But when I have my extension added to the pipeline it seems other parsers are not running or rather some parsers are not running.
In my resulting HTML I do get < p >s everywhere but If I add a strong to my alert text it does not get the tags. If I do not add my extension to the pipeline I do get a tag on my HTML.
Is there something special I need to do to make that work?
This is the syntax I have chosen, Maybe its not good?
markdown = @"¤Tip|This is a tip alert and this text should be strong however it is not if my extension is loaded";
With my extension off:
<p>Tip|This is a tip alert and this text should be <strong>strong</strong> however it is not if my extension is loaded</p>
With my extension on:
<p><div class="alert alert-success" role="alert">
<p class="alert-title">
<strong>
<i class="bi bi-lightbulb"></i>
Tip
</strong>
</p>
<p class="mb-0">This is a tip alert and this text should be **strong** however it is not if my extension is loaded</p>
</div></p>
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 reproducing the reported syntax with the custom InlineParser and HtmlObjectRenderer enabled in the pipeline, then compare the generated HTML with the extension disabled. Trace how the alert content is passed through the pipeline and determine what makes inline strong parsing run; done means the alert text renders strong as strong while the alert markup remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100