From f7996de9848bb58a4406011356d2a20047361f98 Mon Sep 17 00:00:00 2001
From: Yad Smood <1415488+ysmood@users.noreply.github.com>
Date: Tue, 29 Oct 2024 21:08:56 +0800
Subject: [PATCH] remove wrong statement about zustand

---
 README.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/README.md b/README.md
index 48667e6..667247e 100644
--- a/README.md
+++ b/README.md
@@ -64,4 +64,3 @@ Its implementation is not type safe and the return value is not intuitive. It's
 
 The typescript support is not good enough, the API is not intuitive. `stalo` is more like `useState` which aligns with the react API style. Check the [comparison](https://github.com/ysmood/stalo/issues/1). Zustand [Slices Pattern](https://zustand.docs.pmnd.rs/guides/slices-pattern) can cause naming conflict issues.
 `stalo` can naturally scale states by modules and files.
-The setter of zustand must be called within a react component, while the setter of `stalo` can be called anywhere.