Repository navigation
Failing test for an api with two different methods but same route. - #1486
Marcus Bernander (marcusber) wants to merge 1 commit into
Conversation
Vincent Biret (baywet)
left a comment
Vincent Biret (baywet)
left a comment
There was a problem hiding this comment.
Hi Marcus Bernander (@marcusber)
Thanks for the contribution.
I left a comment on the sample you added.
| "version": "1.0" | ||
| }, | ||
| "paths": { | ||
| "/api/v2/someroute/areatype/{index}/{arg}": { |
There was a problem hiding this comment.
this snippet is invalid according to the specification
The following paths are considered identical and invalid:
/pets/{petId}
/pets/{name}
There was a problem hiding this comment.
Thanks for the response. Do I understand this correctly that it would be fine if language below would be renamed to arg and regenerated?
There was a problem hiding this comment.
sure, but as you do so you'd then have to follow JSON conventions and merge the two nodes.
There was a problem hiding this comment.
Of course. I could also include the verb hard coded in the path to keep them seperated.
I guess you're just following the specification, but it makes no sense to me.
Decrease readability or clutter the path. A bit frustrating for something that did pass just fine and now is not, Server handled it well. Clients handled it well. The specification doesn't.
In the end it's just two different endpoints without a direct relation.
Anyways, thanks for your time Vincent Biret (@baywet) to shed some light over the behaviour.
|
no worries, you can contribute to the specification if you think it needs to evolve :) |
No description provided.