invalid queries are really easy to make
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Describe the bug
It's super easy to get the interface to error with "invalid query"
To Reproduce
- enter
StartTime > "2023-08-16T14:29:34-07:00"in to the query interface - choose two status items - e.g. running and complete
- enter
(ExecutionStatus="Running" OR ExecutionStatus="Completed")
Expected behavior
Either not be able do to things in the interface (ok, entering queries manually...fine) that cause errors. Seemingly basic things like choosing completed and running statuses would be nice to have working.
Screenshots
Desktop (please complete the following information):
- OS: macOS
- Browser Safari
- Version 16.2 (18614.3.7.1.5)
Additional context
- Temporal UI 2.17.2
- Temporal 1.21.4
- Postgres 15 as a datastore
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the invalid-query error in the query interface using the reported StartTime filter and the Running/Completed status selection. Compare the manually entered query with the query produced by selecting the two statuses; done means these basic filter combinations no longer produce an invalid-query error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100