-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Web
-
2 - S (<= 1 week)
-
3326
Goals & Expected Results
Users would expect custom data transmitted through the access token to be EJSON deserialized.
Actual Results
The data is not EJSON deserialized.
Steps to Reproduce
- Create a collection of documents and enable custom user data.
- Create a user and a matching document in the collection which contains an undefined value.
- Authenticate the user and read the custom data.
- See how the undefined value is returned as {{
{ "$undefined": true }
}} (see https://docs.mongodb.com/manual/reference/mongodb-extended-json-v1/#undefined-type)
Code Sample
<!---
Please provide a code sample or test case that highlights the issue.
If relevant, include your model definitions.
For larger code samples, links to external gists/repositories are preferred.
Full projects that we can compile and run ourselves are ideal!
-->
Version of Realm and Tooling
- Realm JS SDK Version: Realm Web 0.9.0
- Node or React Native: Web
- Client OS & Version: N/A
- Which debugger for React Native: N/A