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

fix(WizardContext - next): Don't initialize 'currentFooter' to avoid stale props #8646

Closed
jpuzz0 opened this issue Feb 2, 2023 · 0 comments · Fixed by #8647
Closed

fix(WizardContext - next): Don't initialize 'currentFooter' to avoid stale props #8646

jpuzz0 opened this issue Feb 2, 2023 · 0 comments · Fixed by #8647
Assignees
Labels
Milestone

Comments

@jpuzz0
Copy link
Contributor

jpuzz0 commented Feb 2, 2023

Describe the problem
When users want to use local state in the same component as Wizard, and pass that updated state to that Wizard's footer, when that footer is a React element, the local state change is not leading to the state updating in that footer. There are workarounds for this specific use-case mentioned below.

Expected behavior
When using local state in the same component that renders Wizard and specifically a Wizard with a custom footer that is a React element, state changes should be reflected within that footer.

Is this issue blocking you?
Not a blocker. Users can pass a footer as a function that returns a react element or use context wrapped around the Wizard to manage state that is accessible from a custom wizard footer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
2 participants