2 people reported
All time, since Apr 13.
Undefined where filters misbehave
“Both of these examples will return a *random* session when token is undefined, in my example due to bad type information.”
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/4996/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
Undefined values in relational query where filters misbehave. In beta.21 undefined fields are skipped, returning a random session; rc.5 snapshots throw while types still accept undefined.
Is this your bug?
File my report- Where
- relational queries API
- Error text
Error: Unexpected 'undefined' in filter value. Use 'EmptyFilter' if you want the filter field to be skipped.- Versions
- 1.0.0-beta.21 to 1.0.0-rc.5
- How bad
- Security risk: something exposed, or done without permission.
Not quite your bug?
- Query filters accept invalid keys2 people
- Select sends empty column list2 people