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
I'm in a situation where we rely on at least three swagger files for 3rd party APIs that we consume.
Are those swagger files all independent? If that it's the case, then the simplest approach would be to create 3 gradle modules and apply swagger-gradle-codegen on each of the module with a separate input file
Can we turn this question intern a feature request? I think a dozen gradle modules is a bit excessive. 😁
Well, I'd argue that having a dozen modules is actually better than having a single module with 12 input files.
Currently, the generateSwagger is incremental and you can leverage this feature by making sure that you run the generator only for the spec files that actually changed.
Having multiple files as Input of a single task, will most likely result in calling the generator on every single file (even if just one was edited).
I'm in a situation where we rely on at least three swagger files for 3rd party APIs that we consume.
What is the recommendation for setting up a gradle file to generate code for three or several dozen swagger files?
Thanks!
The text was updated successfully, but these errors were encountered: