Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unused definitions are trimmed making it impossible to use them in a parent project that relies on already processed file #58

Open
slonka opened this issue Jan 3, 2025 · 0 comments
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@slonka
Copy link
Contributor

slonka commented Jan 3, 2025

What happened?

Let's say we have a common errors definition. "Project A" doesn't use "Conflict" error response. When bundling OAPI for "project A" the "Confclict" response is removed from the resulting file because it's not used. If a parent project called "Project B" wants to use the "Conflict" response it's impossible to get this from "Project A" (it got trimmed).

Possible solutions:

  • add an option for unused definitions to not be trimmed (per file)
@slonka slonka added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Jan 3, 2025
@lobkovilya lobkovilya added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

2 participants