I have a service with a store which is populated through actions on singin/signup.
I have Login-component with a resource for each of them, signin/up + load data.
The login component doesn't use any of those resources' data itself, but it still "owns" the loading spinner, so Suspense seems a natural candidate.
What would be a idiomatic way to solve/structure this? My cleanest workaround so far is to include a call to a suspense-trigger in the JSX. The trigger is just this: