Hey @bsmith-n4 this gem looks amazing. I am running into enormous problems around the xref problems in jekyll-asciidoc. Unfortunately, your gem isn't solving that out of the box for me, possibly having to do with my URL configuration. The RubyDoc seems incomplete.
I have this in test-page.adoc:
[[test-id]]
== Test Section Heading
And in another file, an xref: <<test-id>>.
When rendered, the first page shows [test-id] (unresolved) and links to /test-page/index.html#test-id, where it should be /path/to/content/test-page#test-id.
So I can see that your extension does something, as it knows what page test-id is on; it just doesn't know where that page is, and somehow it doesn't seem to know the section header associated with that ID.
I appreciate any help you can offer. This looks like it could be a lifesaver.
Hey @bsmith-n4 this gem looks amazing. I am running into enormous problems around the xref problems in jekyll-asciidoc. Unfortunately, your gem isn't solving that out of the box for me, possibly having to do with my URL configuration. The RubyDoc seems incomplete.
I have this in
test-page.adoc:And in another file, an xref:
<<test-id>>.When rendered, the first page shows
[test-id](unresolved) and links to/test-page/index.html#test-id, where it should be/path/to/content/test-page#test-id.So I can see that your extension does something, as it knows what page
test-idis on; it just doesn't know where that page is, and somehow it doesn't seem to know the section header associated with that ID.I appreciate any help you can offer. This looks like it could be a lifesaver.