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

Rich type validation should enable/disable the "Next" button as needed after updating a field #97

Closed
4 tasks
sglavoie opened this issue Oct 6, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@sglavoie
Copy link
Contributor

sglavoie commented Oct 6, 2021

Acceptance

  • Rich types are validated so that the Next button is enabled/disabled as needed.
    • When a wrong selection is made then corrected, the Next button is enabled.
    • When all fields were selected and a wrong selection is made, the Next button is disabled.

Tasks

  • ...

Analysis

When validating rich type fields, modifying a selection should trigger a new check to enable/disable the Next button as needed. The state is updated when a "rich type" is modified but not when the standard "type" is changed.

Standard "type" field is updated → the Next button should be disabled.
Peek 2021-10-06 08-54

"Rich type" field is updated → the Next button should also be disabled.
Peek 2021-10-06 09-06


/cc @nirabpudasaini

@sglavoie sglavoie added the bug Something isn't working label Oct 6, 2021
@SusanBot85
Copy link

@steveoni please confirm that this bug was resolved

@sglavoie sglavoie closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants