-
Notifications
You must be signed in to change notification settings - Fork 76
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
Complex data types couldn't serialize #241
Comments
Hey! I think tit should work. Can you create a minimal repo reproducing the issue so I can check it out? |
This error is thrown by firestore sdk
Output:
@wovalle , it can be fixed by serializing entity to plain object before passing to firestore SDK, e.g. |
This is not necessary. Please read docs: |
I'll take a look at your suggestion @skalashnyk |
1 similar comment
I'll take a look at your suggestion @skalashnyk |
If I'm not mistaken, my pull request (#251) solves this issue. |
Does it? My initial idea with this issue was to create a generic mapping between firestore "primitives" and fields in custom models. Can you provide an example of how would you map a native Reference or GeoPoint with the serialization included in the PR? @danieleisenhardt |
I had read the documentation about complex data types, however I can't make it works.
I have this:
And then I do this:
And then I get this
Value for argument "data" is not a valid Firestore document. Couldn't serialize object of type "GeoP" (found in field "geop"). Firestore doesn't support JavaScript objects with custom prototypes (i.e. objects that were created via the "new" operator).
Is there something I'm misunderstanding?
The text was updated successfully, but these errors were encountered: