-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
Split lichess-api.yaml #309
Conversation
Replace in-file component schema references with external references
Reference external paths in ./tags/<tag>/<path>.yaml
Oh,
might possibly be false positives... 😅 This rule may identify false positives when linting a specification that acts as a library (a container storing reusable objects, leveraged by other specifications that reference those objects). |
Nothing references the now externalized components, components/schemas components/examples , so tell spectral lint to use a ruleset which disables the "oas3-unused-component" rule
🤯 🙈 tree --filesfirst specs/
|
been staring at it for a moment, and I can't decide whether it's better or worse than the single file. I guess we'll try it out and see. |
I saw a blog post about splitting huge openapi files into smaller, maybe more managable, parts,
https://davidgarcia.dev/posts/how-to-split-open-api-spec-into-multiple-files/
I figured there are both pros and cons with splitting a single openapi file...
To make it easier to get a feel for how such a split could work,
I figured I'd just try it out on a branch.
lichess-api.yaml
went from 11000 to 1000 lines,and from 1 to 231 in file count...
I do not know if this is a win or if it is a fail. 😅