Option to only generate code for specific tags/operations

[edonv]

Description

It would be extremely useful to be able to filter which operations are generated code-wise. The Swift OpenAPI Generator has this feature, allowing the OpenAPI document's contents to be filtered before code is generated. It has the following capabilities (examples of which can be found here), filtering by:

• path key,
• tags,
• schemas
• operation ID

The Swift OpenAPI Generator does this right, so I think this could just take notes from their implementation of this feature. Their proposal document for this feature is also extremely detailed in their reasoning for the feature and how they implemented it, and I feel that all the reasoning translates directly to this project.

Proposal

While I'm not sure where exactly in the code this filtering would occur (though probably just at the initial parsing of the YAML/JSON), I imagine the exact config per project could be specified in the Redocly config file, similar to the examples here.

I imagine this would be added as a new field in OpenAPITSOptions, or it'd be in the redocly field.

Checklist

• I can come up with the Redocly config parameters.
• I can look into the codebase and see if I can't figure out where the filtering would happen.