Bhavyai Gupta
Bhavyai Gupta
Because, I am building a GraphQL wrapper on an existing service that doesn't have setters. The REST wrapper on that works without any issues, so I wondered why GraphQL doesn't...
Is there any particular reason why GraphQL mutation need setters? IMHO the parameterized constructors should be enough to create the object using the Jackson deserialization. Thanks.
@robp94 Yeah this one works after I update my constructor with `@JsonbCreator`. Thanks for letting this know!
Want to check, can we have Jackson support for Quarkus GraphQL?
To put it simply, expecting GraphQL mutations to work with `@JsonCreater` annotated constructor rather than to rely on `@JsonbCreator` as [robp94](https://github.com/robp94) suggested.
Not sure if you meant to do it differently (posted reproducer does uses `@JsonCreator`), but I see the exact same error. Tried with quarkus version `2.11.1.Final`. Again, `@JsonbCreator` works but...