2 people reported
All time, since Apr 14.
Query filters accept invalid keys
“This defeats the compile-time safety that's supposed to catch a renamed/removed column.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/drizzle/issues/4946/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Relational query filters accept nonexistent keys without type errors. Invalid keys in where, orderBy, and columns pass type-checking once the object also contains one valid key.
Is this your bug?
File my report- Where
- relational queries API
- Versions
- 1.0.0-beta.20 to 1.0.0-rc.4
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Undefined where filters misbehave2 people
- Select sends empty column list2 people