You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An application employing Markdown may want to resolve "naked links" ([foo]) -- i.e. links with no inline destination -- based on contextual knowledge rather than definitions in the text. A custom LinkReferenceDefinition would allow for that.
The text was updated successfully, but these errors were encountered:
Hmm that's an interesting idea. So you would set all the known LinkReferenceDefinition in the parser builder beforehand? I wonder if it would be even more useful to provide a callback instead, then you'd have more flexibility and e.g. be able to only look up a definition for which there were actual references in the document.
An application employing Markdown may want to resolve "naked links" (
[foo]
) -- i.e. links with no inline destination -- based on contextual knowledge rather than definitions in the text. A customLinkReferenceDefinition
would allow for that.The text was updated successfully, but these errors were encountered: