use-flux-architecture-in-composables

Summary

Do not bundle state, mutations, getters, and side-effects into a single monolithic Composable (e.g., a giant useUser). Instead, decompose logic into 4 specific roles: State Provider, Action, Getter, and Util.

Rationale

• Pure Flux Implementation: At its most granular level, this decomposition mirrors the Flux architecture using pure functions, independent of libraries.
• Components over Monoliths: Components can import only what they need (e.g., just an Action, or just a Getter), reducing coupling.
• Testability: Pure logic (Utils) and State mutation (Actions) can be tested more easily in isolation.