You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
i have a large spec file with alot of apis (jira spec) , i would like to generate only one (or few) specific operations/tags and their relevant schemas
for example lets say i want to generate only searchProjects operation so it will generate the searchProjects api with #/components/schemas/PageBeanProject schema and all dependent schema (used properties schemas , inheritance etc)
i believe this is quite common use case , specs are usually sent as one single file which can be quite huge
Describe the solution you'd like
i want to input operation ids or tags and generate only these apis and their schemas
Describe alternatives you've considered
i read that i can use FILTER=operationId:searchProjects
but this still generates unrelated schema
i assume i could select the apis and the related nested schemas required for these apis but this is very tedious to do for nested models
Is your feature request related to a problem? Please describe.
i have a large spec file with alot of apis (jira spec) , i would like to generate only one (or few) specific operations/tags
and their relevant schemas
for example lets say i want to generate only
searchProjects
operation so it will generate the searchProjects api with#/components/schemas/PageBeanProject
schema and all dependent schema (used properties schemas , inheritance etc)i believe this is quite common use case , specs are usually sent as one single file which can be quite huge
Describe the solution you'd like
i want to input operation ids or tags and generate only these apis and their schemas
Describe alternatives you've considered
i read that i can use FILTER=operationId:searchProjects
but this still generates unrelated schema
i assume i could select the apis and the related nested schemas required for these apis but this is very tedious to do for nested models
Additional context
currently using:
i couldn't find any configuration that does that but perheps I'm wrong
The text was updated successfully, but these errors were encountered: