Enable adding own markdown renderers in builder #361
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The NodeRendererMap refuses to write over the existing entries.
Looking a bit into it, it was because MarkdownRenderer.RendererContext iterates over the nodeRenderFactories in reverse order. This means that the last (i.e. the default) one is added first, making it impossible to override.
There were a few ways to fix this, but looking at the corresponding code in TextContentReader.RenderContext and HtmlRenderer.RenderContext, they iterate over the list of factories in the natural order.
@robinst @sebthom if you agree with the fix, it would be great if it could be included in a release soon :-)