useElmish vs useReducer about feliz HOT 4 CLOSED

Because useElmish is already used in the application, I would stick with useElmish for consistency and because in the future if the component needs to evolve it will avoid a re-write/translation from one system to another.

from feliz.

useReducer is a native React feature which probably explains the lack of documentation around it. https://react.dev/reference/react/useReducer

useReducer and useElmish kind of overlap in term of scope but the main difference is that useElmish should allow to use libraries from Elmish ecosystem like debouncer, etc. Plus as you noted the benefit of generated messages to handle complex.

useReducer was introduced by the React team, to kind of include Redux in React directly without having to install an external dependency. I am not sure if this succeeded in archiving the goal they had in mind.

You can mix them, in your application but I think for consistency it is probably better to stick with one.

from feliz.

Hi @MangelMaxime! Thanks for the insight.

Yes, I understand that useReducer is part of the React api, and also that it was a way to bundle a redux-like solution into React to manage complex state.... this is the reason I'm interested to know if is there is a place for useReducer within our app for simple situations where useState is not sufficient to manage state (because of deeply nested components) BUT useElmish might** be overkill for adding a "simple" state machine into a component. Basically, is useReducer recommended at all within a Feliz app? (or was it only added just for better coverage of the React API?).

After all, the Elmish lib it's tiny, and already loaded in our app.

(** I say might, because useElmish is simple enough to implement! )

Thanks again! Cheers.

from feliz.

Got it! Thanks much... sitcking to useElmish!

from feliz.