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
{{ message }}
This repository has been archived by the owner on Oct 17, 2020. It is now read-only.
What is frustrating you?
The number of actions in reducers is increasing as and when a new feature is added. There are a lot of very similar actions like RAISE_CREATE_SHORT_LINK_ERROR, RAISE_GET_USER_SHORT_LINKS_ERROR, RAISE_GET_CHANGELOG_ERROR and if we follow the same pattern, there will be many more for each of CRUD operations of changelogs, users or shortlinks in admin panel which updates the same global states.
Your solution
We could consolidate based on the type of final action it performs instead of the cause which triggers that action(say RAISE_ERROR_MODAL).
The suggested pattern is already being followed for input validation errors for longLink and alias.
The text was updated successfully, but these errors were encountered:
What is frustrating you?
The number of actions in reducers is increasing as and when a new feature is added. There are a lot of very similar actions like
RAISE_CREATE_SHORT_LINK_ERROR
,RAISE_GET_USER_SHORT_LINKS_ERROR
,RAISE_GET_CHANGELOG_ERROR
and if we follow the same pattern, there will be many more for each of CRUD operations of changelogs, users or shortlinks in admin panel which updates the same global states.Your solution
We could consolidate based on the type of final action it performs instead of the cause which triggers that action(say
RAISE_ERROR_MODAL
).The suggested pattern is already being followed for input validation errors for
longLink
andalias
.The text was updated successfully, but these errors were encountered: