Closed tors42 closed 5 months ago
Oh, the remaining 2 warnings from the lint run,
oas3-unused-component Potentially unused component has been detected. components.schemas.$ref
oas3-unused-component Potentially unused component has been detected. components.examples.$ref
might possibly be false positives... :sweat_smile:
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). https://meta.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules#oas3-unused-component
:exploding_head: :see_no_evil:
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. :sweat_smile: