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
Calculate section level for special sections in the API #1261
Comments
mojavelinux
added a commit
to mojavelinux/asciidoctor
that referenced
this issue
Jun 3, 2017
…arser - coerce level to 1 for special sections defined at level 0 - skip unnecessary level logic in parser and converter as a result
To be more specific, special sections can be defined at level-0 in multi-part books. However, they are treated as level-1 sections. This shift should occur in the parser. (Special sections are defined this way so that they can be siblings of parts instead of nested inside of them). |
mojavelinux
added a commit
to mojavelinux/asciidoctor
that referenced
this issue
Jun 4, 2017
…arser - coerce level to 1 for special sections defined at level 0 - skip unnecessary level logic in parser and converter as a result
mojavelinux
added a commit
to mojavelinux/asciidoctor
that referenced
this issue
Jun 4, 2017
…arser - coerce level to 1 for special sections defined at level 0 - skip unnecessary level logic in parser and converter as a result
mojavelinux
added a commit
to mojavelinux/asciidoctor
that referenced
this issue
Jun 4, 2017
…arser - coerce level to 1 for special sections defined at level 0 - skip unnecessary level logic in parser and converter as a result
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calculate the section level for special sections in the API so that it doesn't leak into client code. Currently, the following code is showing up in the converters to handle what the parser should have dealt with:
You can see it as well in the built-in converters.
The text was updated successfully, but these errors were encountered: