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
It's possible to set dispatchReturn to true explicitly but also accidentally enable dispatchMultiple implicitly by including the full signature of the process hook:
This combination can only ever be an error (the logic cannot end), but redux-logic does not warn you about it until the warnTimeout is reached. It seems like it would be beneficial to log an error in development mode along the lines of "You should not include dispatch or done as arguments to process() if processOptions.dispatchReturn is set to true".
The text was updated successfully, but these errors were encountered:
It's possible to set dispatchReturn to true explicitly but also accidentally enable dispatchMultiple implicitly by including the full signature of the process hook:
This combination can only ever be an error (the logic cannot end), but redux-logic does not warn you about it until the warnTimeout is reached. It seems like it would be beneficial to log an error in development mode along the lines of "You should not include dispatch or done as arguments to process() if processOptions.dispatchReturn is set to true".
The text was updated successfully, but these errors were encountered: