Open austinarbor opened 5 months ago
Oof. This is a catch 22 type of situation. In earlier versions, SPQR had its own logic for detecting bean property elements (related field, getter, setter, constructor parameter), which was causing problems. Version 0.12.4 more directly delegates to Jackson to detect these elements, which it then filters based on its own inclusion rules (e.g. skip elements with @GraphQLIgnore
). And here Jackson detects a conflict and throws an exception before SPQR even gets a chance to filter the ignored element out. As a quick workaround, you can add @JsonIgnore
as that will make Jackson skip the element and avoid the conflict altogether. And I'll see how to improve @GraphQLIgnore
handling to prevent conflicts like this...
Hello, I think a regression has been added with the 0.12.4 release
Using the below models, on 0.12.3 I get the following schema:
However, using the same models on 0.12.4, I get an error during schema generation:
Is the
@GraphQLIgnore
no longer being applied, or is there something else going on?