Pretty much all of our projects that generate an Open API spec are linted and produce the same warnings:

There are some options:
- Tweak the spectral ruleset to ignore these warnings
- Add hooks to the shared library that can easily be added to the DRF spectacular settings
If we use the latter approach, I'd say:
- We can generate an empty servers object or something that's domain-agnostic if nothing is present
- We can extract the operation tags and ensure they're collected + added to the global tags
@swrichards @stevenbal @CharString I'm interested in your opinions whether we should provide the hooks here or just tweak the spectral ruleset (which can be done in https://github.com/maykinmedia/open-api-workflows/blob/4383c70a26f3bc5caafd0423bf451ece69bdffe2/actions/oas-lint/action.yml#L62 I suppose)
Pretty much all of our projects that generate an Open API spec are linted and produce the same warnings:
There are some options:
If we use the latter approach, I'd say:
@swrichards @stevenbal @CharString I'm interested in your opinions whether we should provide the hooks here or just tweak the spectral ruleset (which can be done in https://github.com/maykinmedia/open-api-workflows/blob/4383c70a26f3bc5caafd0423bf451ece69bdffe2/actions/oas-lint/action.yml#L62 I suppose)