release 0.15.0 #18

ccvlad · 2025-02-25T18:41:13Z

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 · 2025-02-26T08:43:27Z

package.json

@@ -1,7 +1,7 @@
 {
  "name": "@connectycube/use-chat",
  "description": "A React hook for state management in ConnectyCube-powered chat solutions",
-  "version": "0.14.4",
+  "version": "0.15.1",


DaveLomber · 2025-02-26T08:47:56Z

src/hooks/useBlockList.ts

+
+  const addToState = (userId: number): void => {
+    setState((state) => {
+      state.add(userId);


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 · 2025-02-26T08:48:24Z

src/hooks/useBlockList.ts

+
+  const deleteFromState = (userId: number): void => {
+    setState((state) => {
+      state.delete(userId);


DaveLomber · 2025-02-26T08:50:41Z

src/hooks/useBlockList.ts

+    }
+
+    if (action === BlockAction.ALLOW && !isBlocked(user_id)) {
+      console.warn("[useChat][useBlockList][update]: user is not blocked");


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

DaveLomber · 2025-02-26T08:50:56Z

src/hooks/useBlockList.ts

+    }
+
+    if (action === BlockAction.DENY && isBlocked(user_id)) {
+      console.warn("[useChat][useBlockList][update]: user is already blocked");


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

DaveLomber · 2025-02-26T15:07:44Z

CHANGELOG.md

+
+### Features
+
+- Implemented blockList users API via `useBlockList` hook.


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

- Implemented Block users API

ccvlad added 2 commits February 24, 2025 19:17

prepared to v0.15.0

bb588ec

draft: block list

bfb5bff

DaveLomber reviewed Feb 26, 2025

View reviewed changes

0.15.0

bbfbeb0

ccvlad changed the title ~~RC-0.15.0~~ release 0.15.0 Feb 26, 2025

removed unnecessary console.warn(...)

c5ac240

DaveLomber reviewed Feb 26, 2025

View reviewed changes

DaveLomber approved these changes Feb 26, 2025

View reviewed changes

updated CHANGELOG.md

883da06

ccvlad merged commit 50e1c72 into main Feb 26, 2025
1 check passed

ccvlad deleted the rc-0.15.0 branch May 1, 2025 12:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

release 0.15.0 #18

release 0.15.0 #18


		### Features

		- Implemented blockList users API via `useBlockList` hook.

release 0.15.0 #18

release 0.15.0 #18

Conversation

0.15.0

Features

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment