Custom callback router loader

[sergiodxa]

Right now the authLoader used in the callback route owns the whole loader, what happens if I want to do something else there? Example instead of doing:

export const loader = authLoader({ returnPathname: '/dashboard' });

I may want to know who the user is to change returnPathname. The only way I can think right now to let me customize it would be to wrap authLoader in another loader and parse the response, but since I don't have access to the session storage (see #2) I can't access the user data from there.

[nickdirienzo]

Relatedly, we have have per-customer subdomains on our app. I may want to redirect to a distinct subdomain based on the logged-in user. I could throw a redirect in onSuccess but that feels like a hack. @PaulAsjes should I file a separate issue for this use case? It felt related to this so figured to start here.