@AnderData The added tests look good overall, but they don’t seem to cover all relevant combinations of annotations and types. It would be helpful to include additional cases to make sure the new behavior is fully validated.

Specifically, please consider adding tests for:

• @NotNull combined with @notblank / @notempty (to confirm they still produce required = true);

• Collection types (List, Set) annotated with @notempty, verifying that they generate appropriate schema constraints (e.g. minItems);

• String fields annotated with both @notblank and @SiZe, ensuring that both restrictions are reflected in the resulting schema.

This would improve confidence that the change doesn’t introduce regressions or subtle differences in how these annotations interact.

@AnderData thank you for the contribution!