Fix a crash when #Preview is followed by a newline #147
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
Owner
|
@vince4 Hi! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Short description 📝
Fix issue #145. Add support for Allman style, or whenever the first brace opening the preview is not on the same line as
#Preview.Solution 📦
Check during #Preview line parsing if it contains a brace and should start counting braces or not.
Instead of adding a flag
hasBraceOnFirstLine, I preferred to make braceBalance nullable. So we assign 0 only when the last brace is closed.Tests 🧪
I added a test case with a simple Preview in Allman style and just added an assertion to an existing test :
test_loadRawPreviewBodiesDefaultEnableAndUrlIsDirectory.