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
= Test document
Take a look at plantuml feature:
plantuml::_assets/test.puml[]
Problem
I'm converting file with the following command: asciidoctor -r asciidoctor-kroki -D out sample/test.adoc
Expected behavior: _assets/test.puml file is propertly resolved relative totest.adoc, whenever I'm located in parent dir or in sample
Actual behavior: I got error:
sciidoctor: ERROR: test.adoc: line 5: Failed to read plantuml file: _assets/test.puml. No such file or directory @ rb_sysopen - _assets/test.puml.
File is only converted correctly when I place _assets dir, relative to location of workdir where I execute command.
Comparision with asciidoctor-diagram
asciidoctor-diagram module properly resolve file, I dont' get error with the following command: asciidoctor -r asciidoctor-diagram -D out sample/test.adoc
Possible issue
kroki extension uses raw target without resolution:
Setup
With the following content in
test.adoc
:Problem
I'm converting file with the following command:
asciidoctor -r asciidoctor-kroki -D out sample/test.adoc
Expected behavior:
_assets/test.puml
file is propertly resolved relative totest.adoc
, whenever I'm located in parent dir or insample
Actual behavior: I got error:
File is only converted correctly when I place
_assets
dir, relative to location of workdir where I execute command.Comparision with asciidoctor-diagram
asciidoctor-diagram
module properly resolve file, I dont' get error with the following command:asciidoctor -r asciidoctor-diagram -D out sample/test.adoc
Possible issue
kroki extension uses raw
target
without resolution:To compare,
asciidoctor-diagram
resolves target withnormalize_system_path
method: https://github.com/asciidoctor/asciidoctor-diagram/blob/9f1f9352bff950df0eae7790a85b5cd85c99c2f0/lib/asciidoctor-diagram/diagram_processor.rb#L396The text was updated successfully, but these errors were encountered: