-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onNext is called on initialization #33
Comments
It shouldn't! |
This issue is stale because it has been open 30 days with no activity. Remove no-issue-activity label or comment or this will be closed in 5 days. |
Looks like a dead repo to me. Even the bot is months too late. |
This issue is stale because it has been open 30 days with no activity. |
in my case, is a UI Component . u can get a ref from Button and trigger it Manually, <WithWizard {steps.indexOf(step) > 0 && ( back )} )} /> set function :() => buttonRef.current.props.onClick() to call |
This issue is stale because it has been open 30 days with no activity. |
|
this will be solved in the v3 release. work is being done on the |
This issue is stale because it has been open 30 days with no activity. |
Wizard's onNext prop is called on the component's mount and not only when firing a next event.
The text was updated successfully, but these errors were encountered: