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
We have stores now and can set data in one action and get it inside another, useActionsResult is used to get actions result from previous actions, it's rudiment and should be removed
The text was updated successfully, but these errors were encountered:
so in last action you return a promise which resolves with value, which will saved as blah. It imposes limitations:
You should have actions beside the property which you wanna parse to
Last action should return desired result
In the same time we have stores and can use action { type: 'any_type', set: 'key_name_in_storage' } at any place in parsing process and use saved value in a rule { get: 'key_name_in_storage' }
That's why I think useActionsResult is redundant and must be removed
We have stores now and can set data in one action and get it inside another,
useActionsResult
is used to get actions result from previous actions, it's rudiment and should be removedThe text was updated successfully, but these errors were encountered: