-
-
Notifications
You must be signed in to change notification settings - Fork 719
Fixes #660: Improve typing/logic for options in decode, decode_complete; Improve docs
#1045
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
Conversation
optionsoptions in decode, decode_complete
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping me when it is ready for review
|
@auvipy this should be ready to review. Note that I changed the documentation to use docstrings/autodoc so that the docs don't get stale (I saw a few cases where that happened). Also added more docs where needed; let me know if you'd rather me separate that into another PR. I still need an answer on whether we want to support the |
options in decode, decode_complete options in decode, decode_complete; Improve docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please fix the merge conflicts?
…lete; Improve docs Original PR #1045 by pachewise Original: jpadilla/pyjwt#1045
… in decode, decode_complete; Improve docs Merged from original PR #1045 Original: jpadilla/pyjwt#1045
Basically trying to remove "Unknown" or "partially unknown" pylance issues. Mostly with
options, but there were a few simple other fixes (kwargs, segments, etc). This showed some minor bugs and a few code smells (passing too many args toapi_jws.decode_complete, for example).PyJWT()is used as a singleton. Do we want to keep theoptionsparam in that case? Wondering because codecov is warning that we don't have a test foroptions is not Nonecase.