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

Adding explanation for clockTolerance on JWTVerifyOptions #731

Closed
wants to merge 2 commits into from

Conversation

d4nt
Copy link
Contributor

@d4nt d4nt commented Nov 5, 2024

I was a little confused about what the clockTolerance option did but the docs didn't help much, so I read the code. Here's a very minor improvement based on what I found.

@panva
Copy link
Owner

panva commented Nov 5, 2024

Hello Daniel, thank you for this added explanation. Can you resubmit this PR from a non-default branch on your fork so that I may fix it up?

@@ -38,6 +38,9 @@ Expected clock tolerance
- In seconds when number (e.g. 5)
- Parsed as seconds when a string (e.g. "5 seconds", "10 minutes", "2 hours").
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can I say, I don't understand how it can be parsed in "seconds" when the input is "10 minutes". Does it mean that human readable formats will be parsed, or that "10 minutes" will be converted to 10 seconds...

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

10 minutes is 600, 10 seconds is 10

@d4nt
Copy link
Contributor Author

d4nt commented Nov 5, 2024

Closing this PR: replaced by #732

@d4nt d4nt closed this Nov 5, 2024
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

Successfully merging this pull request may close these issues.

3 participants