Adding support for CRLF in the parser #189
Merged
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
saminjay
reviewed
Jan 5, 2025
| const propertyRegex = /^\s+([a-zA-Z]+):\s*(.+)/; | ||
| const headerEndCodeStartRegex = /^\s*---\s*```.*\n/; | ||
| const headerEndCodeStartRegex = /^\s*---\s*```.*\r?\n/; |
There was a problem hiding this comment.
It's rarely used anymore but some systems (I think macs) used to use CR or \r for new line. Should we add support for that also?
There was a problem hiding this comment.
I don't think we should worry about that, otherwise everything is going to get complicated, really quickly
dostonnabotov
approved these changes
Jan 5, 2025
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.
Description
People were complaning, so here is CRLF support, might cause issues with snippets code, but oh well.
Type of Change