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

Use a default leeway of 0 #223

Merged
merged 1 commit into from
Sep 1, 2017
Merged

Conversation

travisofthenorth
Copy link

This PR addresses #206. It sets up a hash of defaults (which simply has a leeway value). The spec I added fails with the error mentioned in the issue without this fix.

@sourcelevel-bot
Copy link

Hello, @travisofthenorth! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

@travisofthenorth
Copy link
Author

@excpt I'd love to see this gem get past the 2.0.0 finish line, so please let me know if there is anything I can do to help.

@excpt
Copy link
Member

excpt commented Sep 1, 2017

@travisofthenorth Thank you very much.

Working active on the 2.0.0 release. Estimated arrival 4th of September.

@excpt excpt merged commit 77935e5 into jwt:master Sep 1, 2017
@travisofthenorth travisofthenorth deleted the fix/leeway-nil-error branch September 1, 2017 19:52
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.

2 participants