| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
I added two convenience methods to expose decoded JSON without changing existing behavior. Now you can access both decoded header and payload directly from any DecodedJWT. You can now use: - Decoded payload JSON: decoded.getPayloadJson() - Decoded header JSON: decoded.getHeaderJson()
|
Thank you raising the PR. I have reviewed the changes, but wanted to highlight few things. Exposing decoded header or payload JSON directly may encourage consumers to rely on unverified JWT data, since decoding does not imply signature verification. While the data is already accessible today, adding a dedicated API makes this usage more prominent. Can we adding more intuitive naming as getDecodedPayloadJson() and getDecodedHeaderJson(), this prevents from accidental usage? Thank you |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
I added two convenience methods to expose decoded JSON without changing existing behavior. Now you can access both decoded header and payload directly from any DecodedJWT.
You can now use:
Changes
Please describe both what is changing and why this is important. Include:
References
Please include relevant links supporting this change such as a:
Testing
Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Checklist
Contribution by Gittensor, learn more at https://gittensor.io/