This repository was archived by the owner on Sep 14, 2022. It is now read-only.
Fixes for REST Clients and Multiple HTTP Methods bound to the same Path #1
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.
registered (the original behavior violates REST). For instance, say you have the path /foo and want to register both the POST and DELETE HTTP methods on that path (which is correct for REST). Furthermore, lets assume the following Swagger calls:
swagger.addPost(app, ...);
swagger.addDelete(app, ...);
Only the POST will be added to the "app" instance, as the DELETE will get caught in that if check and only get appended to the API and NOT registered with "app". I am not sure what this logic was intended to do, so I am not sure that the fix is correct. However, it got me around the issue I was seeing.