Support dynamic redirect destinations

Is your feature request related to a problem? Please describe. As mentioned in the limitations, there isn’t built-in support for custom redirect destinations based on the user’s auth status. This limits the usefulness of the redirects.

Describe the solution you’d like and how you’d implement it Allow users to provide functions for the authPageURL and appPageURL config properties that should return the appropriate URL. We could pass either ctx or window to the function, depending on the context.

// ctx would be defined when server-side redirecting, window for client-side
({ ctx, window }) => {
  // some logic
  return '/my-auth-page?next=/my-app/'
}

Is this a breaking change? No. We would still support static values for the config options.

Describe alternatives you’ve considered None

[kmjennison]

@tlays Thanks for the thoughtful feedback! I agree with all of your suggestions.

You mention it’s for the authPageURL and appPageURL config properties, but I assume it would also work for the option parameters of all withAuthXXX functions right ?

Yes

I believe it’s implied, but just for clarity, authPageURL and appPageURL could be provided either as string, or functions right ?

Yes

I’m not sure that passing window in parameters is a good idea.

I agree

Shouldn’t we expose the AuthUser also ?

I agree, this is a good idea

[kmjennison]

Opened an issue to update the documentation and example: #122