Rüdiger zu Dohna
Rüdiger zu Dohna
The client seems to be correct (in Java, let's ignore Kotlin for a moment, as that seems to be a different issue). So only test2 in the server is wrong.
Without the `@Multiple` annotation (which would have to move to the common api), the schema would be: ```graphql type SuperHero { name: String team: Team equipment: Equipment } type Equipment...
I'm fine with a new name, but as the semantic is exactly the same in the typesafe client, we should then rename that, too.
@phillip-kruger: I have several smaller problems that you might be able to help with. 1. The `main` branch doesn't compile (`GraphQLWSSubprotocolHandler` and `GraphQLTransportWSSubprotocolHandler`) 2. In the `main` branch, the `ReferenceCreator`...
Related to https://github.com/eclipse/microprofile-graphql/issues/340
The [GitLab issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/18045) was implemented for release 12.0 ;-) And for what it's worth: Limiting the nesting depth to, say, 5 may not be good enough, security wise: If I...
I have a patch for the tck to show the problem, but I didn't find the correct spot to fix it, as I can't find a way to properly debug....
this is the stacktrace: ``` ERROR: SRGQL012000: Data Fetching Error java.lang.IllegalArgumentException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at io.smallrye.graphql.execution.datafetcher.helper.ReflectionInvoker.invoke(ReflectionInvoker.java:92) at io.smallrye.graphql.execution.datafetcher.DefaultDataFetcher.invokeAndTransform(DefaultDataFetcher.java:33) at io.smallrye.graphql.execution.datafetcher.AbstractDataFetcher.get(AbstractDataFetcher.java:63) at graphql.execution.ExecutionStrategy.fetchField(ExecutionStrategy.java:282) at graphql.execution.ExecutionStrategy.resolveFieldWithInfo(ExecutionStrategy.java:211)...
@jmartisk: it would be really nice, if you could also release a WildFly Feature Pack for 1.8.2.
I guess I'll have to continue testing with WF27 and the RCs for now... going live will have to wait.