cascading queries specification
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Request from business area.
Currently, a query defined on a layer is not cascading. It would be nice to have the option to confiure a cascading query.
Example: a dataset contains the following attributes: HEALTH_AUTHORITY, CITY, BUSINESS NAME
In a cascading (top-down) search, a user chooses Vancouver Coastal as the Health Authority then under City users should only see distinct CITY values where HEALTH_AUTHORITY = 'Vancouver Coastal'. Victoria, for example, would not be among the CITY choices in such a case.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the layer query configuration and the map interface that presents attribute choices. Trace how a selected HEALTH_AUTHORITY affects available CITY values, then define the cascading behavior and verify it with the Vancouver Coastal and Victoria example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100