Adding support for hapi 17.x.x #38
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
+1 for release |
|
Anything we can do to help? |
|
+1 It would be great to get this merged in soon. |
|
Until it’s merged it’s easy enough to just copy the function. |
|
Anyway to get this merged in? cc: @sandrinodimattia |
|
What needs to be done to get this merged in? |
sandrinodimattia
approved these changes
May 23, 2018
|
Any ETA on the release for that fix ? |
|
We wanted to also add #31 so giving the PR author a chance to complete. If not will release shortly for this. |
|
Any ETA for this release? |
|
It was in the 1.3.0 release? 49b5cd4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for hapi-auth-jwt2 8.x.x using Hapi 17.x.x as documented on
https://github.com/dwyl/hapi-auth-jwt2#compatibility
Introduced a new promised based method hapiJwt2KeyAsync