fix(provider): Keep existing metadata on threads or comments instead of overriding them

ueberdosis / hocuspocus

The CRDT Yjs WebSocket backend for conflict-free real-time collaboration in your app.

https://tiptap.dev/docs/hocuspocus/introduction

MIT License

1.34k stars 128 forks source link

fix(provider): Keep existing metadata on threads or comments instead of overriding them #784

Closed bdbch closed 9 months ago

bdbch commented 9 months ago

The new threads functions on the Tiptap collab provider allow users to update threads or comments - however this will override the whole data object even if only one key is updated.

This PR will allow users to update only single keys. @janthurau do you think this makes sense or should we solve this another way?

bdbch commented 9 months ago

After discussing we're opting to just send the correct data from the client since keys can't be deleted afterwards.