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
However in the new docs system, this is being treated as a callout that is missing an explanation and results in the following error:
:: fail: Documentation.Builder.Log[0] Code block with annotations is not followed by a list (/Users/lcawley/Documents/GitHub/asciidocalypse/docs/elasticsearch-hadoop/docs/reference/ingestion-tools/elasticsearch-hadoop/configuration.md:264)
Expected behavior
I think we need some way to indicate that a codeblock doesn't use callouts. Or an escape character or some other way to avoid this being captured as an error (though we wouldn't want that escape character to be picked up when folks cut and paste the example).
Steps to reproduce
Copy the codeblock from aforementioned page and run ./docs-builder -p <path>
Tooling
docs-builder
migration tooling
I'm not sure
The text was updated successfully, but these errors were encountered:
Describe the bug
The example in https://www.elastic.co/guide/en/elasticsearch/hadoop/current/configuration.html#cfg-mapping contains a valid use of angular brackets:
However in the new docs system, this is being treated as a callout that is missing an explanation and results in the following error:
Expected behavior
I think we need some way to indicate that a codeblock doesn't use callouts. Or an escape character or some other way to avoid this being captured as an error (though we wouldn't want that escape character to be picked up when folks cut and paste the example).
Steps to reproduce
Copy the codeblock from aforementioned page and run
./docs-builder -p <path>
Tooling
The text was updated successfully, but these errors were encountered: