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

Come up with mechanisms of specifying/figuring out that some or all endpoints do not need to be migrated to the previous version #62

Open
zmievsa opened this issue Sep 29, 2023 · 0 comments
Labels
enhancement New feature or request research

Comments

@zmievsa
Copy link
Owner

zmievsa commented Sep 29, 2023

For example, if an endpoint was not directly affected, there are no request/response migrations for it, its dependencies didn't reference any schemas changed in the current version, its response model was not related to any changed schemas, and its body was not related to any changed schemas.
Additionally, you could do an easy shortcut for versions with purely side effect changes of skipping generation entirely.

This is all closely related to building a graph of changed schemas in #52 .

@zmievsa zmievsa added enhancement New feature or request research labels Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request research
Projects
None yet
Development

No branches or pull requests

1 participant