Another io-free function refactor with testing. All it does is wrap the jwt.decode + params into decode_id_token. Not much of a improvement on it's own, but it puts the security related code in a directly testable place. It's preparation to consider things like caching the jwk, OIDC, or the async-fork a-sibling functions without copying security critical code in multiple places. I want to propose this first before anything else. a-prefixes would stay only in my fork.
General
- Make sure you use semantic commit messages.
Examples:"fix(google): Fixed foobar bug","feat(accounts): Added foobar feature". - All Python code must formatted using Black, and clean from pep8 and isort issues.
- JavaScript code should adhere to StandardJS.
- If your changes are significant, please update
ChangeLog.rst. - If your change is substantial, feel free to add yourself to
AUTHORS.
Another io-free function refactor with testing. All it does is wrap the jwt.decode + params into decode_id_token. Not much of a improvement on it's own, but it puts the security related code in a directly testable place. It's preparation to consider things like caching the jwk, OIDC, or the async-fork a-sibling functions without copying security critical code in multiple places. I want to propose this first before anything else. a-prefixes would stay only in my fork.
## General
- [x] Make sure you use [semantic commit messages](https://seesparkbox.com/foundry/semantic_commit_messages).
Examples: `"fix(google): Fixed foobar bug"`, `"feat(accounts): Added foobar feature"`.
- [x] All Python code must formatted using Black, and clean from pep8 and isort issues.
- [ ] JavaScript code should adhere to [StandardJS](https://standardjs.com).
- [ ] If your changes are significant, please update `ChangeLog.rst`.
- [ ] If your change is substantial, feel free to add yourself to `AUTHORS`.