Set nav states according to startAtStep #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
- Extract buttns state calculation to function and initialize state from that function in constrctor and when moving between steps.
|
Also added fix to set the buttons state according to the startAtStep |
|
Will this solve the issue where the "Previous" button is not visible when the startAtStep is greater than 0? |
|
@darshan-raj yes, it solves this issue as well. |
|
@avivr thanks very much. It's been tested and merged. @darshan-raj yes this PR fixed it. |
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.
Fixing a bug where navStates are not aligned when using 'startAtStep' prop.
The fix cause the steps to show correct 'done'/'in-progress'/'todo' styles.