The option is replaced with -g (--generator-name).

• -g allows the same values as -l

• See list command for the list of generator name

If you are creating or extending a generator (programmatically), you might have use one of the following parameters: OpenAPI openAPI or Map<String, Schema> allDefinitions or Map<String, Schema> allSchemas. Example methods:

• CodegenConfig#fromOperation(String, String, Operation, Map<String, Schema>, OpenAPI)

• CodegenConfig#fromModel(String, Schema, Map<String, Schema>)

• DefaultCodegen#fromResponse(OpenAPI, String, ApiResponse)

• DefaultCodegen#DefaultCodegen.fromRequestBody(RequestBody, Map<String, Schema>, Set<String>, String)

• DefaultCodegen#createDiscriminator(String, Schema, Map<String, Schema>)

• …​

The parameters (openAPI, allDefinitions, allSchemas …​) are now removed from the methods.

To access the current OpenAPI instance, if you are extending DefaultCodegen you can use the protected openAPI member.

If you are creating your own generator by implementing CodegenConfig, then the setter CodegenConfig.setOpenAPI(OpenAPI) will be called. You can keep a reference on the OpenAPI instance.

The default is to validate the spec during generation. If the spec has errors, they will appear as errors or warnings to the user. This prevents generation of the project.

If you want to switch back to the 3.1.x behavior you can use:

• Set the validateSpec option to false if you are using the Maven or Gradle plugin

• Use the command line option --skip-validate-spec if you are using the CLI

In CodegenModel and in CodegenOperation we use now our own class org.openapitools.codegen.CodegenDiscriminator instead of io.swagger.v3.oas.models.media.Discriminator.

For the templates, this is not an API change, because the same values are available.

If you have your own Codegen class (to support your own generator for example) then you might get some compile error due to the change.

Schema with enum values are mapped to java enum in the generated code. In previous version, when an unknown value was deserialized, the value was set to null.

With 3.2.0 a new option is introduced: useNullForUnknownEnumValue.

• When set to false (default value), an Exception (IllegalArgumentException) is thrown when the value not available in the enum.

• When set to true, unknown values are mapped to null as it was the case in previous versions.

A new option is introduced with #432 to specify the prefix of boolean getters: booleanGetterPrefix. Possible values:

• is: the value used in 3.0.x.

• get: the new default value.

If you use the default value you will see your generated code changing from isActive() to getActive().