We are making resolved a first-class citizen property on
threads. You don’t have to use a
thread’s metadata to set a thread as resolved anymore.
You can upgrade to 2.2 by downloading the latest version of each Liveblocks package you’re using. The easiest way to do that is to run the following command:
If you are not using Comments or are not using the resolved metadata property,
there are no breaking changes for you! However, if you are and have logic based
on the webhook event threadMetadataUpdated, keep reading.
When you upgrade to 2.2, the default
Thread component will update
the thread’s first-class citizen property instead of the metadata. When a thread
is marked as resolved or unresolved, we will send the events
threadMarkedAsResolved
and
threadMarkedAsUnresolved
instead of
threadMetadataUpdated.
Before upgrading to 2.2, you should update your webhook endpoint to process those new events accordingly.
If you use the REST endpoint
Edit thread metadata
to update the metadata resolved, you should instead use the endpoints
Mark thread as resolved
and
Mark thread as unresolved.
Note that updating the resolved metadata property automatically updates the
first-class citizen one.