Nested queries broken
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 122
- PR merge metrics
- No merged PRs in 30d
Description
Using the current version 0.8.0 of the Mirage Chrome Extension, whenever the checkbox "Add joining quere" is selected and "nested" is selected from the "select-joining-query" dropdown, the generated query changes to `{}` instead of generating the nested query wrapper.
Tested on Chrome Canary 70.0.3524.0.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue in the Mirage Chrome Extension by selecting “Add joining quere” and choosing “nested” from the “select-joining-query” dropdown. Inspect the query-generation path for this selection and compare its output with the expected nested query wrapper. Done means the generated query is no longer `{}` and correctly contains the nested wrapper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, typescript
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100