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

Generic error resolution schema #92

Open
Tomboyo opened this issue Aug 10, 2023 · 0 comments
Open

Generic error resolution schema #92

Tomboyo opened this issue Aug 10, 2023 · 0 comments

Comments

@Tomboyo
Copy link
Owner

Tomboyo commented Aug 10, 2023

There are a variety of circumstances we may or may not foresee in which we can't generate code, such as when the specification causes name conflicts. As a user, I do not want to modify the OAS locally because I'd be responsible for complex three-way merges with the source of truth, but if I could write "rules" in a file that override the OAS in order to address specification flaws, that would let me work around issues without compromising the stability/repeatability of my builds.

Consider how such a framework could work, and what categories of problems it could solve. Can Lily emit exceptions that describe the issue and instruct the User how to fix them?

This might replace #86, #90, and #91.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant