fix: support for multiple api decorators on schema class #3165
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.
Support multiple
@ApiExtension
decorators on the schema class. This implementation applies the same fix as #1525 but also for the class, not just for the member functions.This enables you do use multiple
@ApiExtension
(and other mixed decorators) on an API schema definition like this:PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently it is not possible to use the same decorator multiple times on the same class. I.e. using two
@ApiExtension()
decorators will only result in the first one being applied.Issue Number: N/A
What is the new behavior?
This PR fixes this behavior and applies all decorators as expected. It implements the same fix as #1525 but on a class level.
Does this PR introduce a breaking change?
Other information