can I handle a group of useSubmisson?
if an action is still pending (like during a synchronization) and another modification occurs that triggers a second update, how should useSubmission handle this? Would it be better to avoid new action submissions while an update is pending, or is there a pattern you would recommend for handling overlapping updates gracefully?
thanks
5 Replies
There is a plural version called useSubmissions
thanks. Even if the latest submission status is pending, I can still trigger a new action, right?
i think actions are sperated
there should be a global ActionStore where every action state is defined
if one is executed, its state will change, not others
useSubmissions returns an array, where each element corresponds to a useSubmission for each action, arranged in the order the actions were initiated. Is that correct?
I think that's correct