Skip to content
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

Expose EJSON in export #85

Closed
jankapunkt opened this issue Feb 8, 2022 · 2 comments
Closed

Expose EJSON in export #85

jankapunkt opened this issue Feb 8, 2022 · 2 comments

Comments

@jankapunkt
Copy link
Member

We should expose EJSON to the client, importing this package.

Describe the solution you'd like

Adding EJSON to the export in the main js file would allow clients to define custom types that are EJSON-able and store them in a local cache, as well as sending them to the server (if defined there as such as well) via DDP.

Describe alternatives you've considered

Using JSON.stringify replacer and resolver to manually transform these but I am not sure, of an attempt to call to the Server would simply strip these from the call message, since EJSON has an internal lookup for custom types.

Additional context

I could add this to #83 or create an additional PR

@TheRealNate
Copy link
Collaborator

@jankapunkt additional PR would be preferred for cleanliness

@github-actions
Copy link

github-actions bot commented Dec 2, 2022

Closing this issue due to no activity. Feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants