Skip to content
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

Asymmetric API - can set system_time_t, but not get #70

Open
GeneratedNickname opened this issue Oct 28, 2020 · 2 comments
Open

Asymmetric API - can set system_time_t, but not get #70

GeneratedNickname opened this issue Oct 28, 2020 · 2 comments

Comments

@GeneratedNickname
Copy link

The method add_claim has an overload for system_time_t, but get_claim_value does not. One would expect symmetry in that regard.

obj.add_claim(jwt::registered_claims::issued_at, chrono::system_clock::now());
auto iat = obj.payload().get_claim_value<chrono::system_clock::time_point>(jwt::registered_claims::issued_at); // Does not compile.
@arun11299
Copy link
Owner

Thanks! Do you want to send a pull request for it ?

@GeneratedNickname
Copy link
Author

If that helps I probably can. Whatever works best for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants