-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Fix/step order #2153
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
base: master
Are you sure you want to change the base?
Fix/step order #2153
Conversation
|
@Parvinmh is attempting to deploy a commit to the Pean Team on Vercel. A member of the Team first needs to authorize it. |
| step >= this._currentStepSignal.val | ||
| direction === "forward" && | ||
| continueStep === false && | ||
| currentStep !== undefined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be continueStep === false || currentStep !== undefined?
Consider this case, what if there is a step (currentStep !== undefined) but continueStep is false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No — it should remain continueStep === false && currentStep !== undefined because we only want to block the step change when the callback explicitly returns false, and there is an existing step to stay on.
No description provided.