feat: add input.filters.schemas option
#1426
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
melloware
approved these changes
Jun 1, 2024
|
@soartec-lab nice this actually fixes an old issue: #1099 |
|
Thank you for let me know and the related issue 🙌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Status
READY
Description
Fix #1099
i added
input.fliters.schemasoption. Because even if i useinput.fliters.tagsto filter endpoint generation, schema objects are not filtered, resulting in unnecessary files being generated. I can avoid that by usinginput.fliters.schemastogether.Related PRs
none
Todos
Steps to Test or Reproduce
Using the test case I added, we can check.