Fix missing in-arrow to start state #17
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
The start state has to be explicitly specified with an in-arrow; otherwise, the state with number 0 is select by default, which isn't correct in our cases.
Lai-YT
force-pushed
the
fix-missing-arrow-to-start-state
branch
from
72376ec
to
8fac72d
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.
The start state is often not numbered as
0due to the order of state creation, but by default, the start state should be0if no in-arrow is specified. This PR adds an explicit in-arrow to the start state to ensure correctness.This bumps the version to
1.0.3.