What problem does this feature solve?
I currently have Nuxt hooked up to a Rails app with Devise-JWT handling authentication on the backend. It all works well apart from one thing:
When a token expires on the backend, I can't log in again from Nuxt.
The reason is that Nuxt sends the old token along with the login request, and Devise-JWT validates this before checking for the username and password.
What does the proposed changes look like?
I don't think it makes sense to ever send the token along with login requests, because the whole point of a login request is to issue a token. Can Nuxt just skip sending the token when the request is coming from the loginWith() method?
An alternative would be to always delete tokens completely from the store before login requests, and this is what I'm doing to work around this right now.
This feature request is available on Nuxt.js community (#c101) 
What problem does this feature solve?
I currently have Nuxt hooked up to a Rails app with Devise-JWT handling authentication on the backend. It all works well apart from one thing:
When a token expires on the backend, I can't log in again from Nuxt.
The reason is that Nuxt sends the old token along with the login request, and Devise-JWT validates this before checking for the username and password.
What does the proposed changes look like?
I don't think it makes sense to ever send the token along with login requests, because the whole point of a login request is to issue a token. Can Nuxt just skip sending the token when the request is coming from the
loginWith()method?An alternative would be to always delete tokens completely from the store before login requests, and this is what I'm doing to work around this right now.