-
Notifications
You must be signed in to change notification settings - Fork 666
[Firestore] where should use a "type safe" approach #7456
Copy link
Copy link
Open
Labels
api: firestoreIssues related to the Firestore API.Issues related to the Firestore API.library: nodejs-firestoreIssues transferred from another repositoryIssues transferred from another repositorypriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Metadata
Metadata
Assignees
Labels
api: firestoreIssues related to the Firestore API.Issues related to the Firestore API.library: nodejs-firestoreIssues transferred from another repositoryIssues transferred from another repositorypriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
You can currently use any string in the where clause of firestore. When using with converter the fieldPath should be "string safe"
Current implementation:
Proposed implementation (when using with converter) :
where Path: