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
Currently in several parts of the documentation, we are hardcoding the fully qualified class name. So if we refactor the package then the documentation becomes outdated.
Expected Behaviour
Creates an asciidoctor extension for reading package and classname from file directly.
In case of the file is not found we can log a warn message.
Current Behaviour
We need to hardcode the package.
The text was updated successfully, but these errors were encountered:
I know that this would be the logical thing, but if you notice all in Asciidoctor does not fail but just shows warnings. Asciidoctor always tries to do its best not failing. You can test it for example with callouts, you can define a callout that does not exists and you'll receive a warning but not an exception.
Issue Overview
Currently in several parts of the documentation, we are hardcoding the fully qualified class name. So if we refactor the package then the documentation becomes outdated.
Expected Behaviour
Creates an asciidoctor extension for reading package and classname from file directly.
In case of the file is not found we can log a warn message.
Current Behaviour
We need to hardcode the package.
The text was updated successfully, but these errors were encountered: