-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(URGENT) yaml2text nesting fails #347
Comments
yaml2text and json2text support any delimiters supplied after the block definition. The problem here is implementation of nested yaml2text contexts. The snippet you put in the description is quite complex to implement, we cant render nested yaml2text blocks until we render root level block, because it consists of filenames and we cannot render nested blocks without root context. I tried to implement it but have not got any success so far. I need more time on this. |
…s: with_yaml_nested_context, with_json_nested_context, new specs for nested case.
…s: with_yaml_nested_context, with_json_nested_context, new specs for nested case.
Fixed in latest commits, thanks! |
In metanorma/bipm-si-brochure#22 the file:
https://github.com/metanorma/bipm-si-brochure/pull/22/files#diff-8b5e7ad97ed1c17d3424c897e975f844
Uses nesting to define yaml2text within yaml2text. i.e.:
The output (if we switch to use
:mn-document-class: iso
) becomes:This means that the inner yaml2text didn't work at all. I noticed that
yaml2text
expects a source code block (----
), but but this way we cannot enable nesting. We must allow any number of matching--
(from 2-
to n-
);.The text was updated successfully, but these errors were encountered: