Feature: Able to Wrap Components Around ProgressStep, Able to Render Steps Dynamically #91
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
|
would be great! |
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.
it was a great library ... really saved my lot of time during development. there was slight issue, it was more of a logical error. when i tried to render dynamically from children prop in which each child have Progressive Step Wrapper, Steps buttons glitched.
What this code can do
Sometimes due to codebase or logic, ProgressStep cannot alway be the first very first child Component. so with this code we will be able to make ProgressStep grandChild without messing all up of our code.
We can dynamically render ProgressStep within ProgressSteps.