Fields with Getters that are not conforming to Java beans naming conventions are ignored

[schmidti159]

Having a field like this, I would expect it to be present in the json schema, but it is not, when the Jackson module is enabled:

class MyDto {
    private String aField;

    public int getAField() {
        return aField;
    }
}

I saw that FieldScope already has some special handling to support these getters, but the field will be filtered here:

jsonschema-generator/jsonschema-module-jackson/src/main/java/com/github/victools/jsonschema/module/jackson/JacksonModule.java

Line 305 in db77aa1

.noneMatch(propertyDefinition -> declaredName.equals(propertyDefinition.getInternalName())

I prepared a failing test and a workaround in this PR. Feel free to modify to your liking.

[CarstenWickner]

Hi @schmidti159,

The example with the mismatching types (String vs. int) is just an accidental error, right?
I suppose you're only referring to the naming convention.

[schmidti159]

Yes, I am just referring to the naming convention, and accidentally did not match the types.