You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, accessing an object in the state from a container is quickier to write than using its selector.
I would like to know all the advantages of k-redux-factory selectors over the direct use the state.
The text was updated successfully, but these errors were encountered:
k-redux-factory is a lib that aim to access your data as fast as possible.
By using selectors you are safe about our possible internal state restructurations.
In this example if you didn't use our selectors, an upgrade of k-redux-factory could break your application. But if you used our selectors, it wouldn't.
Always prefers using lib API and not its internals, when you can!
Besides that I see these advantages:
We (k-redux-factory) can refactor our code without breaking your application (see previous comment)
You have a standard, always use selectors
You can move your factory around your store definition -> your containers will not have to be fixed
You can memoize selectors if you need to at some point
Sometimes, accessing an object in the state from a container is quickier to write than using its selector.
I would like to know all the advantages of k-redux-factory selectors over the direct use the state.
The text was updated successfully, but these errors were encountered: