release 0.15.0

[ccvlad]

0.15.0

Features

• Implemented blockList users API via useBlockList hook.

import React, { useEffect } from "react";
import { useChat } from "@connectycube/use-chat";

const MyComponent: React.FC<MyComponentProps> = ({userId}) => {
  const { blockedUsers, isBlockedUser, blockUser, unblockUser } = useChat();

  useEffect(() => {
    console.log(`Blocked user ids: ${blockedUsers}`);
  }, [blockedUsers]);

  useEffect(() => {
    console.log(`User (${userId}) blocked: ${isBlockedUser(userId)}`);
  }, [blockedUsers, userId]);

  return (
    //...
    <button onClick={() => blockUser(userId)}>{"Block"}</button>
    <button onClick={() => unblockUser(userId)}>{"Unblock"}</button>
    //...
  );
}

[DaveLomber]

0.15.0

[DaveLomber]

React state should be treated as immutable. In your code, you're directly mutating the existing Set by calling its .add() method, and then returning the same reference. This can lead to issues because React relies on detecting changes via new object references. If the state reference remains unchanged, React might not trigger a re-render.

Let's replaced to

const addToState = (userId: number): void => {
 setState(prevState => {
   const newState = new Set(prevState);
   newState.add(userId);
   return newState;
 });
};

This ensures that you are not mutating the previous state directly and that React will properly update the component when the state changes.

[DaveLomber]

same here

[DaveLomber]

console.warn(`[useChat][useBlockList][update]: user ${user_id} is not blocked`);

[DaveLomber]

console.warn(`[useChat][useBlockList][update]: user ${user_id} is already blocked`);

[DaveLomber]

End user does not work directly with useBlockList , so this can be replaced to

- Implemented Block users API