Rüdiger zu Dohna
Rüdiger zu Dohna
Transactions
The spec should at least mention transactions, as users must be aware of the consequences: when you have multiple mutations within one request, they will be executed in separate transactions....
The MicroProfile starter generates some GraphQL server code, while the Quarkus starter doesn't. And it should include a test using the typesafe client. Maybe it would be possible to reduce...
As reported by @nuratsree in [discussions](https://github.com/smallrye/smallrye-graphql/discussions/880#discussioncomment-1010456), starting Quarkus fails if there's a custom directive with arguments. It works fine in WildFly. I have created a reproducer project [here](https://github.com/smallrye/smallrye-graphql/issues/962).
If a user has access to a field (see #958 and #959), the schema also contains a corresponding directive indicating the roles that are allowed to see that field. E.g....
The schema is limited to the fields a user actually has access to, e.g. only users authenticated as a member of the `admin` role can see a query annotated as...
We already can control access to queries and resolvers simply with standard `@RolesAllowed` et.al. annotations. As discussed in #860, there are situations where the fields of some POJO need access...
Currently, a resolver method can only add a single field to a target type. We could reuse the `@Multiple` annotation from the typesafe client to allow resolver methods to add...
E.g. a `@RolesAllowed("admin")` can prevent a client from actually using a query, mutation, subscription, or field. Then it shouldn't be in the schema, and trying to use it should create...
Expose the BeanValidation annotations as GraphQL custom directives, e.g.: ```java class Person { @Email String email; } ``` ```graphql input Person { email: String @email } ``` As the BeanValidation...
When I add a `@NonNull` to the element type of a list, the resulting list still should be nullable. ```java @GraphQLApi public class Boundary { public @Query String foo(List strings)...