Skip to content

Conversation

@Parvinmh
Copy link
Contributor

No description provided.

@vercel
Copy link

vercel bot commented Nov 11, 2025

@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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@Parvinmh
Copy link
Contributor Author

#2136

@Parvinmh Parvinmh added the bug label Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants