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
This would be a wholesale enhancement, and I don't know how common it might be. It isn't just listing blocks; This could happen for links in code font as well, unless Asciidoctor also transforms those.
Does it make sense to parse the output HTML for links instead and not pull them from Asciidoctor node objects? The problem with this is that a broken link cannot then be traced by to a specific file and line number.
The text was updated successfully, but these errors were encountered:
This would be a wholesale enhancement, and I don't know how common it might be. It isn't just listing blocks; This could happen for links in code font as well, unless Asciidoctor also transforms those.
Does it make sense to parse the output HTML for links instead and not pull them from Asciidoctor node objects? The problem with this is that a broken link cannot then be traced by to a specific file and line number.
The text was updated successfully, but these errors were encountered: