[suggestion] Get apis property from either SystemProperties or additionalProperties#4937
Conversation
…ed in SystemProperties
| String apiNames = GlobalSettings.getProperty(CodegenConstants.APIS); | ||
|
|
||
| if (apiNames == null || StringUtils.isBlank(apiNames)) { | ||
| apiNames = (String) opts.getConfig().additionalProperties().get(CodegenConstants.APIS); |
There was a problem hiding this comment.
I don't think this will work… it would mean that generators can no longer support an apis additional property for other reasons as any setting here would cause no API classes to get generated.
Can you provide an example of how you've configured the Maven plugin? I think it would be best to fix system property support there.
|
@shybovycha I've tested the following, and it works as expected: This generates only |
|
Thanks for submitting this PR and for proposing workarounds here and in #4938. I'm going to close this in favor of #5251, which adds an |
Introduction
There is one quite nifty but undocumented option,
apis, which could be set in system properties. It defines which API groups should be generated. Given the undocumented internal behavior of grouping all operations by tags, this gives an easy way to migrate existing projects to Open-API with minimal changes by automatically generating API definitions and then generating API interfaces with operations automatically grouped according to the existing endpoints.Hence I am creating a few PRs (#4937, #4938, #4939) addressing this hidden gem of
openapi-generator.This change
I could not really find a good way to pass values through
SystemPropertieswhen using the maven plugin. Hence it is pretty much impossible from my point of view to set theapisproperty, I think that it could also be passed through theadditionalPropertiesoption.Also, see the other PR ( #4938 ) which fixes a bug in parsing the list options in
additionalProperties.Does not seem like a breaking change, hence targeting
master.PR checklist
./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).master,4.3.x,5.0.x. Default:master.