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
From my perspective, I think payload is used for data that is necessary to update a given state to a new state whereas meta can be used for literally anything, commonly middleware. It's extra Information.
A good example of using meta is redux-effects, where it's used to define future step()s for an effect. This is not necessary for updating the current state but for the middleware:
This commit includes structural changes in the way the subject is
updated. It uses destructuring and universal updateSubject function
for updating both name and scores. The actions are built with resepct to
Flux Standard Action, but don't contain meta property.
This is due to this topic:
redux-utilities/flux-standard-action#18
id and subjectsType are essential for all the actions so they're kept
in payload
Right now it is a bit diffuse when one should use
meta
overpayload
. Some more descriptive examples might be a good idea?The text was updated successfully, but these errors were encountered: