Reference links aren't resolved about premonition HOT 6 CLOSED

Back to the issue :)

The initial reason for rendering inside Premonition instead of a fall-through strategy, was that I needed to insert variables into the render. But I will see if I can come up with another approach.

from premonition.

Thanks for reporting this. Haven't actually crossed my mind that this could be a problem. I will look into this and see if I can come up with a fix.

from premonition.

Some of these features (reference links, footnotes, etc) were important to me, so I went ahead and wrote my own plugin for content blocks to solve this problem. It's quite rudimentary right now, and not very configurable for the moment, so be warned!

@lazee, the section called "How does it work?" in the README of my plugin explains the approach, and may be a source of inspiration for a fix. The key idea is that the Markdown content of a block shouldn't be parsed separately from the rest of the document.

If premonition fixes this issue, I would be happy to archive/deprecate my plugin and recommend premonition instead.

from premonition.

@MaximeKjaer Cool, I will definitely look into this!

If you are interested, I'll be happy to let you in on the project itself. Probably a lot of cool stuff that are yet to be added :)

from premonition.

Sure, I can help out on the project! Can't promise a ton of time in the coming weeks, but when I do have time, I'm up for it.

from premonition.

Removing the rendering within premonition is actually not that simple. Instead I have introduced support for reference links, like this: #19

from premonition.