We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just reading through the header for basic_claim and can see there is no as_object() to match the as_string(), as_array() and other similar functions
basic_claim
as_object()
as_string()
as_array()
Not good with the standard by any means - but from the spec
For JWTs, while claim names are strings, claim values can be any JSON type
Of which an object should be fine. Is there a reason for as_object to be omitted or is this an oversight?
object
as_object
I can make a pull if its an oversight
The text was updated successfully, but these errors were encountered:
oversight would be possible. I think it simply was not required to handle the JWTs structure, signing or verification.
I am certainly in favor of this. Please open a PR.
It's possible to use to_json() as an alternative.
to_json()
Sorry, something went wrong.
Closing as resolved
No branches or pull requests
Just reading through the header for
basic_claim
and can see there is noas_object()
to match theas_string()
,as_array()
and other similar functionsNot good with the standard by any means - but from the spec
Of which an
object
should be fine. Is there a reason foras_object
to be omitted or is this an oversight?I can make a pull if its an oversight
The text was updated successfully, but these errors were encountered: