-
-
Notifications
You must be signed in to change notification settings - Fork 554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FieldPath.documentId doesn't exist #1117
Comments
Did you see this? |
yep, I've been using |
Not sure why the statics wouldn't be available on the instance returned from useFirestore, but you should be able to be pull straight from the firebase SDK (since it is just a static): import firebase from 'firebase/app'
import 'firebase/firestore'
// Then later
firebase.firestore.FieldPath.documentId() @dsgriffin Thanks for sharing the workaround, that is also valid! |
@prescottprue no worries! just tried using discovered that |
it works for me.... import firebase from firebase/firestore const collectionRef = collection(db, 'myData'); |
Do you want to request a feature or report a bug?
Bug
(If this is a usage question, please do not post it here—post it on gitter. If this is not a “feature” or a “bug”, or the phrase “How do I...?” applies, then it's probably a usage question.)
What is the current behavior?
FieldPath
does not exist onFieldPath
when retrieving via theuseFirestore
hook.What is the expected behavior?
Trying to retrieve multiple documents in one go via
in
insideuseFirestoreConnect
e.g. this should work:But the only property that exists on
FieldPath
currently isisEqualTo
.If I try to use
firebase
directly e.g.I get a ton of type issues and cannot proceed.
Which versions of dependencies, and which browser and OS are affected by this issue? Did this work in previous versions or setups?
Latest Stable (3.10.0)
The text was updated successfully, but these errors were encountered: