Call Field Visibility Per Request in Quarkus GraphQL

[nirue]

I would like to call field visibility per request in Quarkus GraphQL in order to restrict the visibility of the schema per user.

Is there any way to achieve this?

public GraphQLSchema.Builder beforeSchemaBuild(@Observes GraphQLSchema.Builder builder) {

    var codeRegistry = GraphQLCodeRegistry.newCodeRegistry(builder.build().getCodeRegistry())
        .fieldVisibility(new CustomVisibility())
        .build();

    return builder.codeRegistry(codeRegistry);
}

This works, but it does not allow me to pass the user object in a thread-safe manner.

---

public GraphQLSchema.Builder beforeSchemaBuild(@Observes GraphQLSchema.Builder builder) {
        var codeRegistry = GraphQLCodeRegistry.newCodeRegistry(builder.build().getCodeRegistry())
            .fieldVisibility(new CustomVisibility())
            .build();

        return builder.codeRegistry(codeRegistry);
}

public class CustomVisibility extends DefaultGraphqlFieldVisibility {

    @Override
    public List<GraphQLFieldDefinition> getFieldDefinitions(GraphQLFieldsContainer fieldsContainer) {
        User userContext = CDI.current().select(User.class).get();
        IO.println(userContext.getName());
        return super.getFieldDefinitions(fieldsContainer);
    }
  
    @Override
    public GraphQLFieldDefinition getFieldDefinition(GraphQLFieldsContainer fieldsContainer, String fieldName) {
        User userContext = CDI.current().select(User.class).get();
        IO.println(userContext.getName());
        return super.getFieldDefinition(fieldsContainer, fieldName);
    }   
    
}

@Unremovable
@Dependent
public class User {
    
    @Inject
    CurrentVertxRequest request;

    @ActivateRequestContext
    public String getName() {
        if (request.getCurrent() != null) {
            IO.println(request.getCurrent().request().getHeader("user"));
        }
        return null;
    }
}

This solution works, but I'm unsure whether it will lead to other problems.

After some tests, I came around that this solution does not work either because the schema is not rebuilt.

I am grateful for any help.

[quarkus-bot[bot]]

/cc @jmartisk (graphql), @phillip-kruger (graphql)

[jmartisk]

Unfortunately no, this is not supported at the moment. This would need deeper integration that builds separate schemas at build time for each user...

[nirue]

Thank you for your answer.