(protographic) rpc Resolve method generation does not work if there are no arguments

[flymedllva]

Component(s)

router

Component version

0.105.2

wgc version

0.105.2

controlplane version

router version

What happened?

Description

I don't understand how to make a resolver for a field without arguments. For this kind of scheme, a resolver is not generated

type Meow @key(fields: "id") {
    id: ID!
    superMeows: [SuperMeows!] @connect__fieldResolver(context: "id")
}

As I understand it, this happens because of if (field.args.length === 0) return in collectResolverRpcMethods, but I want to have a separate method (rpc) for resolving this field.
In order for the desired behavior to work, I need to come up with an argument like:

type Meow @key(fields: "id") {
    id: ID!
    superMeows(noop: Boolean): [SuperMeows!] @connect__fieldResolver(context: "id")
}

Expected Result

Gen rpc Resolve* without input in type field

Actual Result

Not gen rpc Resolve* without input in type field

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Package Manager: pnpm, npm, yarn, etc
Compiler(if manually compiled): (e.g., "go 14.2")

Router configuration

Router execution config

Log output

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.

[flymedllva]

I expect this to work similarly to the @goField directive with forceResolver true, generating a separate method for resolving the field https://gqlgen.com/config/#inline-config-with-directives

[Noroth]

Hi @flymedllva.

Initially the field resolvers design was a way to handle fields inside of a type that have arguments. In Protobuf we don't have a concept for this, so in order to resolve dynamic data for a field we came up with this.

But we are currently working on making field resolvers available for any field that is annotated with @connect__fieldResolver

#2629