getodk / getodk/web-forms

Add support for empty state to <select>, <select1> and <rank>

Open
#294 7 comments 0 reactions 0 assignees View on GitHub
deferred
Dominant language
TypeScript
Stars
38
Forks
22
PR merge metrics
No merged PRs in 30d

Description

**Description**

The ``, `` and `` question types can use the [choice-filter](https://docs.getodk.org/form-logic/#filtering-options-in-select-questions) to limit options (itemset) based on the answer to a previous question. In some cases, all options may be filtered out, leaving these question types empty, i.e., not displaying any option in the UI.

**To do:**
- [ ] Research and determine priority
- [ ] Design a consistent user interface and experience for this empty state.
- [ ] Implement the empty state in ``, `` and ``.
- [ ] Automate tests to verify the UIUX

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing how choice-filter results are rendered for , , and , then read the linked filtering-options documentation for expected behavior. Define a consistent empty-state experience and its priority before implementation. Done means all three question types display the agreed state when filtering removes every option, with automated UI tests covering it.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.