feat(open-api-gateway): support singular tags on operations #276
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 change adds support for tagging operations, for example:
Previously, tagging would cause broken lambda handler wrappers etc to be generated since the CDK construct assumes a single
OperationConfig
, and tagging APIs caused multiple to be generated.In this change, we always generate a single
OperationConfig
, but iterate over all apis to make sure all operations for all tags are included.We change the default configuration for the Smithy openapi projection to preserve tags since if they are specified in the model users would expect them to apply to the generated code/documentation etc. This means that operations can be tagged in the Smithy model like so:
This behaviour can be overridden in the project's
smithyBuildOptions
, ie:re #269