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

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 · May be fixed by mtech-31-quemistry/quemistry_client_web#20
Labels
Type: Bug Issue contains a defect related to a specific component.
Milestone

Comments

@Jagan-P
Copy link

Jagan-P commented Jul 3, 2024

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

  1. Open the stackblitz link
  2. Click on "Next" button. It will not go to next step if we update currentStep which is being used for the prop activeStep
  3. If we use stepperRef.current.nextCallback() then it works

Expected 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.

@Jagan-P 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 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
@melloware

This comment was marked as outdated.

@melloware melloware added the Type: Bug Issue contains a defect related to a specific component. label Jul 3, 2024
@melloware
Copy link
Member

@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