start_after(None) and the like should be a no-op and shouldn't result in an error #439
Labels
api: firestore
Issues related to the googleapis/python-firestore API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Attempting to execute a query with a start_after(None) will fail. This should be a no-op.
I'd expect start_after, start_at, end_at, end_before to manage a None field handed to them.
The text was updated successfully, but these errors were encountered: