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

feat: expose some types #595

Merged
merged 1 commit into from Nov 20, 2023
Merged

feat: expose some types #595

merged 1 commit into from Nov 20, 2023

Conversation

himself65
Copy link
Contributor

@himself65 himself65 commented Nov 6, 2023

I'm trying to implement some end-to-end encryption updates, like encryptUpdate(update, private) -> update, that allows the server to merge updates and decode updates...(just like obfuscateUpdate), but the difference is contents are encrypted by privateKey. So that it can be safely saved to the server, but the update is still valid so that the server can validate if the document schema is correct.

Then, I found that some internal classes are not exposed, so it will make things hard to extend the existing logic. I would appreciate it if some internal types could be exposed to the downstream so that we can make the ecosystem better.

Huly®: YJS-445

@himself65
Copy link
Contributor Author

@dmonad any idea of this PR?

@dmonad dmonad merged commit b531438 into yjs:main Nov 20, 2023
2 checks passed
@dmonad
Copy link
Member

dmonad commented Nov 20, 2023

Sure, gonna make a release soon!

@himself65 himself65 deleted the expose-content-doc branch November 20, 2023 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants