-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Resource referencing] Multi-Step Form with Stepper - V2 Mandatory fields #423
Comments
@ChaimaaZaoui our stepper already handles Next/Previous buttons state. However we need to add validation rules for ShareData steps 3 and 4. We can either create a dedicated ticket to handle both step validation states, If we create a new issue, we can copy the following spec for step validation rules: Tech SpecValidation Domain
This domain must expose :
Several schema validation libraries can be used to help for forms input validation, such Zod. Apply validation to the step
|
@0xLodz this issue is mainly about the validation when mandatory fields are completed. I just reminded the general functioning to link it to the initial US. |
@ChaimaaZaoui for share data step 3,
Thanks. |
As a user,
I want to have a clear understanding of my progress in a multi-step form by visualizing it through a stepper component,
and I want to be able to navigate through the form using Next and Previous buttons.
Acceptance criteria
Scenario 1: Moving forward
Given that I am on a specific step of the Resource referencing process,
When I have completed the required fields on the current step,
Then the
Next
button should be active which allows me to proceed to the next step.Given that I am on a specific step of the Resource referencing process,
When I have not completed the required fields on the current step,
Then the
Next
button remain inactive and non-clickable.Given that I am on the last step of the Resource referencing process,
Then the
Next
button should be hidden.┆Issue is synchronized with this Wrike task by Unito
The text was updated successfully, but these errors were encountered: