Robert Pospisil

Any news on this?

If I remember correctly, the quarkus version still uses jsonb. If you don't have setters, you need to do something like this for the server input objects https://github.com/smallrye/smallrye-graphql/blob/3f7a7ab79ade1b049a73ff4a0e66128d171ee7d3/server/integration-tests-jdk16/src/test/java/io/smallrye/graphql/tests/records/RecordTest.java#L103

Is there an update to this issue?

https://youtrack.jetbrains.com/issue/KT-13228 If you add the compiler option `-Xemit-jvm-type-annotations` or for maven do it like this ``` -Xemit-jvm-type-annotations ``` The annotation is present in the java byte code and gets picked...

Looks nice. Does it support mutiny return types? Would this already work with quarkus? Then we could test it with our services and see if we find anything.

Hm since the quarkus properties do not work at the moment i use this config at the moment: `smallrye.graphql.errorExtensionFields=exception,classification,code,description,validationErrorType,queryPath` So there should be the code `validation-error`?

The one I posted above. With a custom exception where I use the annotation, I get the error code: ``` { "errors": [ { "message": "Test", "locations": [ { "line":...

[code-with-quarkus-validation.zip](https://github.com/smallrye/smallrye-graphql/files/7396329/code-with-quarkus-validation.zip) ``` { "errors": [ { "message": "validation failed: query.testObject.test darf nicht leer sein", "locations": [ { "line": 1, "column": 9 }, { "line": 1, "column": 15 } ], "path":...

@t1 Have you looked into this? Or could you link me your reproducer?

Would be nice to have this.