Set parameters when using JWT.decode #64
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use the
JWT.decodemethod quite often. I believe it is less resource intense (idk), and easier to implement, because you don't have to set all the check parameters.One thing that's always getting on my nerves is that the function doesn't set the necessary attributes of the JWT object, which makes it harder to work with (arguably not much harder but harder nonetheless).
I'm not sure whether this is a brilliant idea or not. As far as I can tell, nothing should break, but there were no tests and I didn't want to write my own, so I couldn't really test. I added documentation though that lets devs know to use this values with caution as they are not checked.