(protographic) Support for custom `directives` for `connect`

[flymedllva]

Component(s)

router

Is your feature request related to a problem? Please describe.

Support for custom directives for connect

Describe the solution you'd like

Support for custom directives for connect

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

[endigma]

Hi @flymedllva, can you share more about your use case?

[flymedllva]

If you declare a custom directive in the graphql file for cosmo connect, no code for interacting with the gRPC generated service is offered, as is done in gqlgen.

[endigma]

Can you share more about what kinds of directives you’d like to see?

It’s easier for us to triage and understand your issues if you can tell us your user story of what leads you to want a feature, how you would use it, how you might envision it working, this applies to all of your newly opened feature requests for connect as well.

[flymedllva]

Let's say I want to create a directive like @skipAuth (so that all RPC methods are closed by default with auth verification).
To do this, I could declare directive @skipAuth on FIELD_DEFINITION in GraphQL, but I have no way to use this in a gRPC service (generated by .proto).
In gqlgen, I generate a method for working with the directive, and I can also access this directive via AST within the context of any middleware, which is very convenient, gqlgen doc: https://gqlgen.com/reference/directives/#restricting-access-based-on-user-role

It may be worth throwing the directive into rpc with the protobuf option, for example:

rpc MutationTest(MutationTestRequest) returns (MutationTestResponse) {
    option (service.directives.skip_auth) = true;
  };

But we must not forget that this is a simple example; directives can also have parameters, and we need to come up with something clearly more complex.

[endigma]

Hi @flymedllva, thanks for sharing. We'll take a look at this proposal internally.