Skip to content
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

Open
RareSecond opened this issue Oct 17, 2018 · 9 comments
Open

onNext is called on initialization #33

RareSecond opened this issue Oct 17, 2018 · 9 comments
Milestone

Comments

@RareSecond
Copy link

Wizard's onNext prop is called on the component's mount and not only when firing a next event.

@zaguiini
Copy link

It shouldn't!

@asutedja asutedja added this to the v3 milestone Dec 11, 2019
@github-actions
Copy link

github-actions bot commented Apr 8, 2020

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.

@RareSecond
Copy link
Author

Looks like a dead repo to me. Even the bot is months too late.

@github-actions
Copy link

github-actions bot commented May 9, 2020

This issue is stale because it has been open 30 days with no activity.

@wowtrxqn
Copy link

Wizard's onNext prop is called on the component's mount and not only when firing a next event.

in my case, is a UI Component . u can get a ref from Button and trigger it Manually,
even u can set css display: none to hidden UI ,

<WithWizard
render={({ next, previous, step, steps }) => (


{steps.indexOf(step) > 0 && (

back

)}

)}
/>

set function :() => buttonRef.current.props.onClick() to call

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity.

@ryhinchey
Copy link
Contributor

ryhinchey commented Mar 4, 2021

onNext probably shouldn't be called on initial render. That'd solve for #33.

@ryhinchey
Copy link
Contributor

this will be solved in the v3 release. work is being done on the 3.x branch

@github-actions
Copy link

github-actions bot commented Aug 5, 2023

This issue is stale because it has been open 30 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants