Skip to content

Warn if no models, instead of throwing an error #67

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

Merged
merged 2 commits into from
Apr 20, 2024

Conversation

jamesnw
Copy link
Contributor

@jamesnw jamesnw commented Apr 15, 2024

Adds a Warning message instead of throwing an error if no models file is found.

Ideally, we would check if components.schemas or components.parameters is defined, but the OpenAPI definition is not in scope here.

I didn't see prior examples of throwing errors, and I'm very open suggestions on what should be done there instead.

Fixes #66

Copy link
Collaborator

@seriouslag seriouslag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. A healthy change 👽

@seriouslag seriouslag added the bug Something isn't working label Apr 15, 2024
@seriouslag seriouslag requested a review from 7nohe April 15, 2024 23:47
@7nohe 7nohe merged commit 42c0ca9 into 7nohe:main Apr 20, 2024
@jamesnw jamesnw deleted the warn-no-models branch April 21, 2024 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error No models file found after upgrading to v1
3 participants