commonmark
Change ordering of `node.getNext()` and `context.render(node)` in CoreHtmlRenderer.java
Getting the next node before rendering the current one prevents a renderer from contextually unlinking the next node.
Hmm, not sure how I feel about unlinking nodes during rendering. Can you explain how you're marking use of this? I'm wondering if it would be better to do this in a preprocessor step (e.g. could replace both nodes with a custom one).
Hmm, not sure how I feel about unlinking nodes during rendering. Can you explain how you're marking use of this? I'm wondering if it would be better to do this in a preprocessor step (e.g. could replace both nodes with a custom one).
On mobile so can’t do a full write up of what I’m running in to but the gist is. I’m trying to render obsidian links/images.
I have a custom link processor for that here but this has a side effect of creating nodes that I have to collapse hackily during rendering here.
Hey @silentbaws. Both places you linked are just in CustomLinkProcessor, did you mean to link somewhere else? Do you have an example of what syntax you're trying to parse and how you want to render it? (I had a look at your repo but couldn't see any tests.)
Happy to reopen if more information is provided. From what I can tell a PostProcessor should work for your use case.