effector-patterns

Best practices for reactive state management with Effector include using sample to derive state, attach to inject dependencies, combine to aggregate stores, and domain composition to organize events and effects safely.

Use sample to derive reactive state and trigger effects based on specific store combinations, and use attach to inject dependencies into effects, ensuring robust and testable functional patterns in your frontend code.

Using getState() inside Effector reducers breaks reactive state consistency and is a common anti-pattern; safe alternatives include using sample to pass the necessary state explicitly into your events and effects.

Structure domain-based stores, events, and effects by grouping related state logic into domains, using combine to aggregate multiple stores and sample to derive state, ensuring safe reactive code organization.

Effector patterns support complex frontend state composition through combine for aggregating state, sample for deriving new stores, and attach for effect composition, enabling robust reactive code without unsafe state access.

Common Effector anti-patterns include using getState() inside reducers and bypassing reactive flows; safe alternatives use sample, attach, and combine to maintain pure functional state management and prevent inconsistent reactive updates.