-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document breaking changes in v7 #283
Comments
setting |
|
It would be nice if we could choose the name of the property that is used to store the token. For my part, the name |
released as |
Cannot set nested objects anymore using v8.2.1 with req: {
...
payload: {
foo: "bar"
},
"payload.user": object // the payload of token
...
} Instead of adding |
@boobo94 thank you for reporting this, I've reverted to the previous behavior in |
everything works great. thanks for your help <3 |
Would be nice to have some instructions on how to upgrade from v6 to v7 in either the README or Changelog. The Changelog only mentions
which I took to mean it was an internal rewrite, with no breaking changes.
But as far as I can tell there at least these two major changes that require users to modify their code:
import { expressjwt } from 'express-jwt'
req.auth
rather thanreq.user
The text was updated successfully, but these errors were encountered: