Use a function for options.redirect to inject Nuxt Context

[gtnsimon]

What problem does this feature solve?

I'm using @nuxtjs/auth module in a Nuxt App for building a SaaS product where URLs contains the customer ID (e.g: https://nuxt.app/acme/login). In Nuxt, it could be represented to an URL like so in the router: /:customerId/login (in this example, :customerId is equal to acme).

Long story short : I have a Nuxt server middleware that checks if acme is an existing customer in database. If yes, I add it to req.customerId and finally insert it into my store using Nuxt Store nuxtServerInit action. I now know the customer ID and can access it from ctx.store.customerId.

In the current implementation of options.redirect, we can use:

• false to disable redirects
• an object to define custom paths

It would be nice to have access to the Nuxt Context when defining options.redirect so URLs can depends on and solve my needs (and others peoples too).

What does the proposed changes look like?

We could use a function to define URLs for options.redirect :

// nuxt.config.js
{
  auth: {
      redirect: function (ctx) {
          return {
              login: `/${ctx.store.customerId}/users/sign_in`
          }
      },
  }
}

Allowed return types should remain : false, object.

I did take a look in the source code of the Auth class used by the plugin, and redirects are handled by Auth.redirect function. Modifying it to check if it is a function is not a big deal.

It is also called from the auth middleware, that have access to the context.

I've tried on my machine but the problem is with defaults options. options.redirect is dropped and the middleware return an error : ctx.$auth.options.redirect is not a function which is normal.

Thanks for your help and your awesome plug-and-play auth module!

_{This feature request is available on Nuxt community (#c513)}