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 was archived by the owner on Nov 24, 2019. It is now read-only.
If I select next and try and work with it programmatically, redux-query will throw undefined as that promise hasn't resolved. Thus my workaround is to create a new object without mutations to prevent side affects, then return the object. This works, but has the side affect of not triggering rerenders on components dependent on this. So, in this instance, if I update the contact and return to view the proposal summary tab, the contact is the same.
Take this code block for instance, where we are contact types for a proposal in the store as
state.db.proposalIf I select
nextand try and work with it programmatically, redux-query will throw undefined as that promise hasn't resolved. Thus my workaround is to create a new object without mutations to prevent side affects, then return the object. This works, but has the side affect of not triggering rerenders on components dependent on this. So, in this instance, if I update the contact and return to view the proposal summary tab, the contact is the same.