Module resolve 

Field → resolver jump.

gqls owns the schema; rq owns the code. Given a schema field (or type), we encode graphql-ruby’s naming conventions as a prioritized list of rq queries, run rq --json for each, and merge the hits — so “where does Query.user resolve?” lands on Resolvers::User / def user in the server codebase. Naming varies across apps, so we try several conventions and rank by (convention priority, then rq’s own confidence) rather than guess one.

Structs

RqHit

One code definition rq found, plus the candidate query that surfaced it.

Functions

candidates

graphql-ruby query candidates for a record, highest-priority first. Uses rq’s qualified syntax (Class#method, Module::Class).

resolve

Resolve rec to its code definition(s) via rq, best first. schema_path, when a local file, ranks hits by package proximity to the schema — the resolver in the schema’s own subgraph wins over a same-named one elsewhere.