fix: ensure PATCH operation IDs are unique #66
Merged
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.
This PR fixes:
PATCH
operation IDs as long as their existingGET
operations have unique IDs. This should easily handle any operation that can be split bycasing.Split
, e.g.get-foo
,get_foo
,getFoo
, orGetFoo
and turn it intopatch-foo
. If the operation doesn't start with aget
orfetch
, then we just prependpatch-
to the existing operation ID.Additionally:
application/problem+json
like other errorsPATCH
operations now all have a default description set for documentation.Existing tests continue to pass and provide coverage for the modified code.