Do not redecorate the request object if already decorated#152
Merged
jaw187 merged 2 commits intohapijs:masterfrom Feb 17, 2017
gordysc:master
Merged
Do not redecorate the request object if already decorated#152jaw187 merged 2 commits intohapijs:masterfrom gordysc:master
jaw187 merged 2 commits intohapijs:masterfrom
gordysc:master
Conversation
Contributor
Author
|
@jaw187 hope you had a great holiday season! Any shot we could get this merged in/reviewed? |
|
+1 this feature should be great... |
Closed
Contributor
Contributor
Author
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have a separate PR opened against Hapi to allow for someone to check if a request object is already decorated with a method. However, that should only affect people using HapiJS 16.0.X. This PR can be used with previous versions of Hapi, as the underlying logic is still there.
This addresses #119