-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Stepper: Changes to activeStep
prop does not change the step
#6820
Closed
Jagan-P opened this issue
Jul 3, 2024
· 2 comments
· Fixed by #6841, leoo1992/GeradorQRCode#80 or leoo1992/GeradorQRCode#85
Closed
Stepper: Changes to activeStep
prop does not change the step
#6820
Jagan-P opened this issue
Jul 3, 2024
· 2 comments
· Fixed by #6841, leoo1992/GeradorQRCode#80 or leoo1992/GeradorQRCode#85
Comments
Jagan-P
added
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Jul 3, 2024
melloware
removed
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Jul 3, 2024
This comment was marked as outdated.
This comment was marked as outdated.
melloware
added
the
Type: Bug
Issue contains a defect related to a specific component.
label
Jul 3, 2024
@Jagan-P nevermind that is Steps and you are using Stepper. It looks like a bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The Stepper component accepts an input prop named
activeStep
. Changes to that prop does nothing currently. It should ideally go to that step.Reproducer
https://stackblitz.com/edit/vitejs-vite-zxyarp?file=src%2FApp.tsx
PrimeReact version
10.6.6
React version
18.x
Language
TypeScript
Build / Runtime
Create React App (CRA)
Browser(s)
No response
Steps to reproduce the behavior
currentStep
which is being used for the propactiveStep
stepperRef.current.nextCallback()
then it worksExpected behavior
Updating the
activeStep
prop should also work. It should take us to that particular step. Or else there is no point of having this prop.The text was updated successfully, but these errors were encountered: