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

Differentiate between a user skipping the rank question and consciously choosing the default order #295

Open
4 tasks
latin-panda opened this issue Jan 30, 2025 · 1 comment

Comments

@latin-panda
Copy link
Collaborator

Note: This is different from issue #294. This issue is about the question’s value (user input) held internally in the form.

Description
The current rank implementation is incomplete because there is no way to differentiate between a user skipping the question and consciously accepting the default order.

Additionally, rank questions need a way to clear their value and reset to the initial state.

Questions

  • If a rank question is required, and the user has not reordered the options from their default order, should it be considered unanswered?

Additional Details
Both Collect and Enketo start with an empty answer and only populate the response when the user takes explicit action.
In line with this behavior, Enketo allows clearing a rank question’s value, resetting it to the initial disabled state.

To do:

  • Research and determine priority
  • Design a consistent user interface and experience for this empty state.
  • Implement the empty state in <select>, <select1> and <odk:rank>.
  • Automate tests to verify the UIUX
@latin-panda
Copy link
Collaborator Author

@eyelidlessness added good context here that relates to this issue more closely and that should be considered during design

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant