Add support for custom params on the OPERATION OBJECT #45
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
z0mt3c
added a commit
that referenced
this pull request
Aug 29, 2015
Add support for custom params on the OPERATION OBJECT
|
thanks |
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.
The swagger 2.0 spec supports custom params on the operation object when the param starts with x-
http://swagger.io/specification/#operationObject
This PR implements this fictionality, maintains 100% code coverage and implements the needed unit test.
The API This adds is on the happy rout config, under the hapi-swaggered namespace, we now have a
customparam that allows any key name that starts withx-and has a string value.