fix: remove myst_parser required extension to allow for other extensions like myst_nb that conflict #1064
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
|
Please ensure linting passes |
Danny213123
changed the title
Danny213123
changed the title
Danny213123
changed the title
Danny213123
force-pushed
the
Danny213123-patch-1
branch
from
71824a4 to
8343a95
Compare
…ons like myst_nb that conflict
Danny213123
force-pushed
the
Danny213123-patch-1
branch
from
8343a95 to
576b2dc
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.
fix: remove myst_parser required extension to allow for other extensions like myst_nb that conflict