Add option to deconflict errors with same status code for OpenAPI #1995
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 closes #1649. See also: #1265.
It re-introduces a subset of the changes that were added previously in #1304, but later reverted in #1334. The docs changes from #1304 were not entirely reverted, so those are modified here to reflect the new changes, which include only allowing for the
oneOf
option to deconflict errors. Contrary to the docs for the previous PR,oneOf
is supported by API Gateway when theoneOf
is included within a component schema and referenced via a$ref
. UsingoneOf
within the path content directly is not allowed.Deconflicting errors is opt-in when converting to OpenAPI by setting the following in smithy-build.json:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.