Closed TheHelias closed 5 months ago
If our typing expects you to use Union[Literal["ASCENDING"], Literal["DESCENDING"]]
, then why do we use Query.ASCENDING
and Query.DESCENDING
in tests and examples? What are the guarantees that Query
properties do not change?
If our typing expects you to use
Union[Literal["ASCENDING"], Literal["DESCENDING"]]
, then why do we useQuery.ASCENDING
andQuery.DESCENDING
in tests and examples? What are the guarantees thatQuery
properties do not change?
Fair point, would at least make sense to use them in the typing as well.
Usually I dislike having strings in the code, so I'd like to use readily defined constants, and there they are already defined. If those change in the Firebase SDK, I guess that would then inflict changes to Firedantic as well anyway. I wouldn't expect those to change though.
The same set of changes were submitted as a second PR https://github.com/ioxiocom/firedantic/pull/63 that was merged. Closing this one.
Add order_by, limit and offset as options in find query parameters Updated urllib3 for fix vulnerabilities