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

🛠️ [TASK] : User Input Component - Yes/ No #1412

Open
2 tasks
Tracked by #1410
mike-mcnulty opened this issue Dec 17, 2024 · 3 comments
Open
2 tasks
Tracked by #1410

🛠️ [TASK] : User Input Component - Yes/ No #1412

mike-mcnulty opened this issue Dec 17, 2024 · 3 comments
Assignees
Labels
F14 ux/ui UX/UI related issues

Comments

@mike-mcnulty
Copy link

mike-mcnulty commented Dec 17, 2024

Summary

As a proposer, I need to be able to answer yes/no questions, so that I can indicate whether certain criteria apply to my proposal. I may need conditional questions to appear based on my response, so that I can provide additional details about my answer.

Use Cases:

  • Translation
  • Open Source

Acceptance Criteria

  • No answer should be selected by default
  • Allow configuration for conditional questions ie IF select "yes" THEN show additional plan text question AND THEN don't allow save until secondary question completed as well (@seankdesigns this piece needs a little love - refresh screenshots afterwards)

Designs

https://www.figma.com/design/1e1MMDXyi0oL9sG9IunWL7/UI-Kit-Figma-for-catalyst?node-id=5271-49626&t=gTh3B1j2eYONQrjf-0

Default
Property 1=Default

Selected
Property 1=Default Selected

Editing
Property 1=Editing

Filled
Property 1=Filled

@seankdesigns
Copy link

@mike-mcnulty Designs updated & added to ticket

@dtscalac
Copy link
Contributor

@mike-mcnulty
If a Yes/No is selected and saved, should the user be able to revoke the answer? I.e by tapping again on Yes/No the value would be unselected (like initially before giving any answer).

@mike-mcnulty
Copy link
Author

@dtscalac i think we just force user to switch if they've already made selection. doesn't seem to be much sense in un-selecting - it either is, or isn't. if i haven't saved an initial selection already, i can effectively "un-select" by just closing the edit state without saving. could also be funny edge case for our saving approach, since the component is checking validations before the response can be saved.

@seankdesigns @nielskijf any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F14 ux/ui UX/UI related issues
Projects
Status: New
Development

No branches or pull requests

3 participants