Allow users to specify a new start rule after having initialized their Parser class #101
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
BlakeCThompson
force-pushed
the
allow_specifying_start_rule_after_class_initialization
branch
from
288bd94 to
803f4a7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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, in order to test subcomponents of a grammar, you must manually change the start attribute of the user defined parser class, and then rerun any tests using text from the subset.
With the changes in this PR, users can specify a "start_override" string to rebuild the grammar with the new start value. This allows developers the ease of testing subsets of the grammar without having to create several versions of their parser, or editing their parser before testing each sub-rule of the grammar.
Unit tests passing