Fix #40: trim spaces when parsing, not rendering #41
Conversation
This file contains hidden or 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
Trailing spaces from string blocks were not rendered, even when the block was created using Mark.New.string. This commit removes trimming when string is rendered and instead adds trimming to string block parser. That way documents parsed from string behave the same as before, but programmatically inserted whitespace is preserved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Trailing spaces from string blocks were not rendered, even when the block was created using Mark.New.string. See #40.
This PR removes the trimming when string is rendered and instead adds trimming to string block parser. That way documents parsed from string behave the same as before, but programmatically inserted whitespace is preserved.