docs: finalized wiki integrity maintenance (v3.0 standard) - pruned 1400+ stubs and fixed 11k+ ghost links
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
[[상태 관리 최적화 (Zustand, Valtio)]]
|
||||
[[상태 관리 최적화 (Zustand, Valtio)|상태 관리 최적화 (Zustand, Valtio)]]
|
||||
📌 Brief Summary
|
||||
Optimizing state management involves choosing the right tool for the specific reactivity needs of the application. Libraries like Zustand (Action-based) and Valtio (Proxy-based) offer different paradigms to reduce boilerplate and minimize re-renders compared to traditional solutions like Redux or React Context.
|
||||
|
||||
@@ -18,8 +18,8 @@ Optimizing state management involves choosing the right tool for the specific re
|
||||
* **Transient Updates:** Updating store values without triggering a React render (reading directly via `api.getState()`).
|
||||
|
||||
🔗 Knowledge Connections
|
||||
* Related Topics: [[React 상태 관리 (React State Management)]], [[Redux 등 상태 관리 (State Management)]], [[Reactive-Programming]]
|
||||
* Projects/Contexts: [[Skybound Protocol UI]], [[Skybound Mission Persistence]]
|
||||
* Related Topics: [[React 상태 관리 (React State Management)|React 상태 관리 (React State Management)]], [[Redux 등 상태 관리 (State Management)|Redux 등 상태 관리 (State Management)]], [[Reactive-Programming|Reactive-Programming]]
|
||||
* Projects/Contexts: Skybound Protocol UI, Skybound Mission Persistence
|
||||
* Contradictions/Notes: Proxy-based state (Valtio) can sometimes hide where updates are coming from, making debugging harder in large teams if strict conventions aren't followed.
|
||||
|
||||
Last updated: 2026-04-18
|
||||
|
||||
Reference in New Issue
Block a user