-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Footnote backrefs #15
Comments
Yup; that's being added what we're actually using on the backend to render the final HTML spat out by Tiptap (since we need to be able to render tiptap and 'plain' Markdown to the same final artifact), which is the |
In terms of extending the extension to achieve this — I am not sure we want to be so heavily prescriptive as to default to adding the backref, but I think we could absolutely expose a hook to allow overriding the render (which would also solve #11). |
That makes sense, @jmduke. Thanks for sharing what y'all are doing. Just added render-time backref processing to Pika. Thanks! (I'm assuming this issue can be closed, but I'll leave that up to you!) |
In Buttondown I see a footnote resolved with a backref link. See here:
In my usage the footnote doesn't render with a backref. I end up with something like:
Without the backref link that I see on Buttondown:
I don't find any instances of
backref
in the repo, so I'm wondering if you're extending the extension in Buttondown to achieve this?The text was updated successfully, but these errors were encountered: