Export the built-in parser macros individually #429
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
jcking
previously approved these changes
Apr 12, 2021
TristonianJones
force-pushed
the
expose-macros
branch
from
2aef118 to
7aaffeb
Compare
TristonianJones
force-pushed
the
expose-macros
branch
from
7aaffeb to
db752ea
Compare
|
PTAL @jcking |
jcking
reviewed
Jun 30, 2022
jcking
approved these changes
Jul 1, 2022
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.
Currently marcos are either custom, all, or none. This change exposes the builtin
parsermacros by name, making it easier to customize the macro set enabled for the application.