feat(parser/renderer): support explicit line breaks #195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xcoulon
force-pushed
the
Issue189_explicit_line_break
branch
from
4c18c43 to
3c123ed
Compare
supported with the ` +` suffix in paragraph lines, with the `[%hardbreaks] attribute on a paragraph and with the `:hardbreaks:` attribute at the document level. also, refactoring in the renderer to remove some functions that can be replaced with native templates functions, and simplify others. fixes bytesparadise#189 Signed-off-by: Xavier Coulon <[email protected]>
xcoulon
force-pushed
the
Issue189_explicit_line_break
branch
from
3c123ed to
b1ccebb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
supported with the
+suffix in paragraph lines,and the `[%hardbreaks] attribute on a paragraph.
fixes #189
Signed-off-by: Xavier Coulon [email protected]