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
I have a container component that renders several other container components. Some of those children container components don't show up in the router match but still have data they need to load. It'd be great if there was some way I could explicitly specify in the parent's asyncConnect to call its children's async tasks.
The text was updated successfully, but these errors were encountered:
This way if the ChildContainer is in the route match, then it'll trigger the asyncConnect. If not, then the parent must know this and explicitly add it to its own asyncConnect. Works for me, any feedback on this method?
I have a container component that renders several other container components. Some of those children container components don't show up in the router match but still have data they need to load. It'd be great if there was some way I could explicitly specify in the parent's asyncConnect to call its children's async tasks.
The text was updated successfully, but these errors were encountered: