-
Notifications
You must be signed in to change notification settings - Fork 2
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
Schema should be loaded from the file and not embedded #41
Comments
It could also use helper methods. Instead of:
we could have:
|
The biggest difficulty is that schemas/ directory is populated from #definitions. But 1) there could be spec files without any definitions and all schemas embedded directly in endpoint description or 2) spec file could partly use definitions and partly embeds. The safest solution would be creating directory I need to test it with various spec files to look for the best solution. For now I moved schema validation to separate class . |
Referenced schema can be also used as part of other schema, ie array of Pets:
|
Currently we're embedding schemas in our endpoint definitions. It bloats Python files and make it harder to navigate through them. If several endpoints use the same schema, you need to modify it in multiple places.
We should use path to schema instead - we're already preserving schema json files.
The text was updated successfully, but these errors were encountered: