We've released custom metadata for comments, an always use knowledge setting for AI Copilots, and an improved quickstart flow.
Join thousands of companies using Liveblocks ready‑made collaborative features to drive growth in their products.
This January, we’ve made improvements to Comments, AI Copilots, onboarding.
To use the latest features, update your packages with the following command.
If you were previously on Liveblocks 3.10 or below, make sure to follow our upgrade guides before updating.
It’s now possible to add custom metadata to individual comments, enabling a host of use cases such as two-way synchronization with external applications like Slack, custom comment types, and more.
Previously, Liveblocks allowed you to add custom metadata to each individual thread, essential for enabling custom thread-level functionality, such as assigning users, adding tags, attaching X/Y coordinates, and more. With the latest release, each comment can now contain custom metadata, allowing for additional comment-level functionality.
Let’s take a look at how this can be used.
Comment metadata now allows for two-way synchronization with external applications such as Slack, meaning that when a user replies to a comment in your application, the reply will be automatically synced to Slack, and vice versa.
Slack stores IDs for each message, and using comment metadata, you can now store these IDs in individual comments.
Additionally, you can now create custom comment types and render them however you wish. For example, you could create a custom poll comment, and render this component inside your thread.
To create this, you could store poll data directly inside comment metadata.
You can then create your own thread component, choose to render this any way you
like, for example with a custom Poll component, alongside
Comment and
Composer.
Next month we’ll be releasing an improved way to customize components in your
thread directly with the
Thread component, meaning
you can keep its benefits—such as displaying unread comment messages.
AI copilots in our dashboard can internalize knowledge—uploaded files and submitted websites—which the AI can use to answer questions on your data. Copilots now have a new setting that allows you to force AI to read your knowledge base before answering, ensuring each reply is relevant and accurate. To enable it, visit your dashboard and check the “Always use knowledge” option.
It’s also possible to enable this setting when modifying your copilot programmatically.
We’ve thought through our whole onboarding flow, and created a new interactive quickstart section that helps you find specific guides for your use case and technology more quickly than ever. You can also just skip right to getting your API keys.
Alongside the new flow, we’ve added a number of new guides on setting up Liveblocks Notifications, and a new guide for creating a collaborative Tldraw whiteboard. This update lays the groundwork for more get started guides, which will be coming soon!
Liveblocks interface.createThread, createComment, and editComment to
attach and update comment metadata.editCommentMetadata method to update only a commentʼs metadata.useCreateThread, useCreateComment, and
useEditComment to attach and update comment metadata.useEditCommentMetadata hook to update only a commentʼs metadata.commentMetadata prop to Composer to attach and update comment
metadata.commentMetadata prop to FloatingComposer to attach and update comment
metadata.createThread, createComment, and editComment to
attach and update comment metadata.editCommentMetadata method to update only a commentʼs metadata.commentMetadataUpdated webhook event.enableDebugLogging to better debug
connection issues.CommentBody types.Composer and AiComposer would throw an error when
mounted/unmounted.LiveList state in UI.Composer and AiComposer would throw an error when
mounted/unmounted.Toolbar in @liveblocks/react-tiptap not reflecting the editorʼs
current state.create-liveblocks-app CLI.To use these latest features, update your packages with:
Contributors include:
6 authors