Liveblocks is a platform to ship collaborative features like comments, notifications, text editors in minutes instead of months.
@liveblocks/react
useInboxNotificationThread
hook to createLiveblocksContext
, which can be used to retrieve threads within thread notifications for more flexibility.startsWith
operator to useThreads
when filtering based on metadata.@liveblocks/react-comments
InboxNotification
component via the kinds
prop and the InboxNotification.Custom
component.--lb-destructive
, --lb-destructive-foreground
, and --lb-destructive-contrast
)@liveblocks/node
triggerInboxNotification
method that lets you trigger custom notification kinds.getRooms
method. This works via query.roomId
, metadata
is deprecated and is now query.metadata
.getRooms
and getThreads
methods.getRooms
and getThreads
methods, which supports exact matches and the startsWith
operator.@liveblocks/react-comments
@liveblocks/node
process
is undefined" issue in Vite builds. This issue was already fixed for @liveblocks/core
, but not for @liveblocks/node
yet.@liveblocks/node
updateRoomId
method that lets you update the room ID of the specified room.guid
parameter to sendYjsBinaryUpdate
and getYjsDocumentAsBinaryUpdate
to point to a Yjs subdocument with the specified guid.@liveblocks/react
scrollOnLoad
option to useThreads
: enabled by default, this option controls whether to scroll to a comment on load based on the URL hash.useUser
and useRoomInfo
no longer support returning nothing. Returning undefined
will now be treated as an error.useUser
and useRoomInfo
returned an extra data
superfluous property.createLiveblocksContext
would conflict with the provided Client
.@liveblocks/react-comments
InboxNotification
with a single action for now: marking as read.Comment
/Thread
.Comment
background color when it’s linked to or being edited.process is not defined
could happen@liveblocks/react-comments
bn
) and Hindi (hi
).showRoomName
prop on InboxNotification.Thread
wasn’t
applied to notifications about mentions.@liveblocks/react
useEditThreadMetadata
would result in a
brief flash of the old metadata after the metadata was removed optimistically.@liveblocks/client
@liveblocks/react-comments
InboxNotification
.@liveblocks/react
useThreads
, useRoomNotificationSettings
, and
useInboxNotifications
during initial fetching.This release introduces Notifications (and unread indicators) for Comments.
create-liveblocks-app
createLiveblocksContext
and Notifications to --init
.createRoomContext
to createClient
and add
resolveRoomsInfo
to the list of resolvers.@liveblocks/client
createClient
: resolveUsers
, resolveMentionSuggestions
(both were previously defined on createRoomContext
from
@liveblocks/react
), and the new resolveRoomsInfo
.@liveblocks/react
LiveblocksContext
accessible with createLiveblocksContext
,
similarly to createRoomContext
. This context is meant to live at the root
since it handles things outside of rooms, like notifications. It contains
LiveblocksProvider
, useUser
, useRoomInfo
, useInboxNotifications
,
useUnreadInboxNotificationsCount
, useMarkInboxNotificationAsRead
, and
useMarkAllInboxNotificationsAsRead
.createRoomContext
: useMarkThreadAsRead
,
useThreadSubscription
, useRoomInfo
, useRoomNotificationSettings
, and
useUpdateRoomNotificationSettings
.createLiveblocksContext
and
createRoomContext
: useUser
, and useRoomInfo
.@liveblocks/react-comments
InboxNotification
and InboxNotificationList
.Thread
component.@[email protected]
is now a valid mention and
will trigger resolveMentionSuggestions
with "[email protected]"
)@liveblocks/node
getInboxNotification
, getRoomNotificationSettings
,
updateRoomNotificationSettings
, and deleteRoomNotificationSettings
methods)NotificationEvent
.Thanks to @marcbouchenoire @nimeshnayaju @nvie @FlowFlorent @ofoucherot @jrowny @adigau