@BeanParam enum field losing type and enum when @Schema(defaultValue)…

[Pepo48]

… is set

• merge type, enum and format from the Java field type into the existing partial schema when it has no type set

Closes: #2595

[sonarqubecloud]

Quality Gate failed

Failed conditions
76.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[MikeEdgar]

Thanks for the PR @Pepo48 . I plan to review later today/tomorrow. I'm wondering if this issue affects schema handling generally and not just for parameters. E.g. does it happen for a property within another schema as well?

[Pepo48]

@MikeEdgar I also wondered about this earlier and at least based on what I see from my research is that it doesn't affect schema properties. The POJO property pipeline handles this correctly via TypeProcessor.processType(), which resolves enums before @Schema is read.

The bug is in mapParameterSchema() in AbstractParameterProcessor, which handles all parameter types, not just @BeanParam fields. Verified on @QueryParam and @HeaderParam, both as @BeanParam fields and direct method arguments. In all cases, parameterHasSchema() returns early when any schema object exists, skipping type resolution entirely.

But, please, recheck this thoroughly, just to be on the safe side. 😊

[MikeEdgar]

@Pepo48 pardon the delay, I am still thinking through this one. Your change works well for the narrow set of attributes in the new logic (type, enumeration, format), but really the issue impacts any type that is currently not being introspected. Granted, this can easily be worked around by adding implementation = SomeClass.class to the @Schema annotation nested within the @Parameter, but I think it might be best to handle it generally for more than just enumerations.