Disable GitHub flavored Markdown when lexing #2317
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
Mrtenz
approved these changes
Apr 8, 2024
GuillaumeRx
approved these changes
Apr 8, 2024
FrederikBolding
force-pushed
the
fb/disable-gfm-on-markdown-lexing
branch
from
ac2b723
to
13bd3ad
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.
markedhas GitHub flavored Markdown enabled by default, but we don't support GitHub flavored Markdown in the UI. This makes the validation stricter than it needs to be. This PR fixes that by disabling GitHub flavored Markdown when lexing.