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
However, when the action fires during the rehydration process, the action has no key attribute attached.
My alternate method (which seems to work) is to simply pull out the relevant part of the state tree from action.payload, and implement my custom rehydration logic there:
case REHYDRATE:
conststartedMoment=moment(action.payload.forms.newAppointmentForm.startedMoment)returnObject.assign({},state,{ startedMoment })
Could you confirm that this is the "new" way of doing things, and that the docs are just out-of-sync with the API?
Thanks!
The text was updated successfully, but these errors were encountered:
As per the "Custom Rehydration" section in recipies.md, I implemented a
case REHYDRATE
statement in my reducer.However, when the action fires during the rehydration process, the action has no
key
attribute attached.My alternate method (which seems to work) is to simply pull out the relevant part of the state tree from
action.payload
, and implement my custom rehydration logic there:Could you confirm that this is the "new" way of doing things, and that the docs are just out-of-sync with the API?
Thanks!
The text was updated successfully, but these errors were encountered: