graph_weaver 0.7.1 → 0.7.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e0ae9c23b2566bfa26c786e07703e4fad357cbd09a29112d3e0c9dd5d3af916c
-  data.tar.gz: fb5f4534174e5ba9cb7b9d323af26c2a13456c022f8682bcc3ccae5e512a1c96
+  metadata.gz: 653ecbcc2215bf5358e34bc83d701ded874a6ee1910ceeca18f0ed205a44798f
+  data.tar.gz: 2d1e49f247e84347c7bd86123b54b1b9d31d8978bc2a6a8f8d9538342c3ab67d
 SHA512:
-  metadata.gz: dc780e4f155ea89b9977822a7bb62ed9880d3b7e707fd5046229b1c91c843a9c1ec37c39fb5e2039e71c9095dfb7a0df006347a19ce4544f75f2b3fe13a35a5c
-  data.tar.gz: 3dcc86b06e670408ebc18eaaaad7447d5825d1d580b9640ed8860133ba29908eb42553d52da4a2619eb23f072f4999f5aceb622271fafc8d5431fd57a3106ed3
+  metadata.gz: 220c5d9ab87c671a602b226b2789fee65307e3b8a85407fa5c979eb272cde0e27d551e0a6d5ef32ad2714a6eec211fcf0657d1a2b7eb7a53c33d063756d8e82c
+  data.tar.gz: 650c62d1ca107aaaccfa03ddd4686475c15ad68c0cf421be67379a7b88212af8366681da61208dee39ee2a68a468ca792f8cc9fee54c8982087924f927c2a2d1

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    graph_weaver (0.7.1)
+    graph_weaver (0.7.3)
       graphql (>= 2.6.7)
       sorbet-runtime
 
@@ -195,16 +195,16 @@ GEM
     rubydex (0.2.7-x86_64-darwin)
     rubydex (0.2.7-x86_64-linux)
     securerandom (0.4.1)
-    simplecov (1.2.0)
-    sorbet (0.6.13485)
-      sorbet-static (= 0.6.13485)
-    sorbet-runtime (0.6.13485)
-    sorbet-static (0.6.13485-aarch64-linux)
-    sorbet-static (0.6.13485-universal-darwin)
-    sorbet-static (0.6.13485-x86_64-linux)
-    sorbet-static-and-runtime (0.6.13485)
-      sorbet (= 0.6.13485)
-      sorbet-runtime (= 0.6.13485)
+    simplecov (1.3.0)
+    sorbet (0.6.13498)
+      sorbet-static (= 0.6.13498)
+    sorbet-runtime (0.6.13498)
+    sorbet-static (0.6.13498-aarch64-linux)
+    sorbet-static (0.6.13498-universal-darwin)
+    sorbet-static (0.6.13498-x86_64-linux)
+    sorbet-static-and-runtime (0.6.13498)
+      sorbet (= 0.6.13498)
+      sorbet-runtime (= 0.6.13498)
     spoom (1.8.3)
       erubi (>= 1.10.0)
       prism (>= 0.28.0)
@@ -299,7 +299,7 @@ CHECKSUMS
   google-protobuf (4.35.1-arm64-darwin) sha256=d9c957df04fa89c749fa9a72a7b383eb4296efc9b2303dc6fd6fbe39c698ad6b
   google-protobuf (4.35.1-x86_64-darwin) sha256=66b62b4df00931018a692806df66393efa960d6d2b7da69735187249f950d3ee
   google-protobuf (4.35.1-x86_64-linux-gnu) sha256=c786439087512a3fbd199e9897d265b855f951d4027e218ea55e858d45969edd
-  graph_weaver (0.7.1)
+  graph_weaver (0.7.3)
   graphql (2.6.10) sha256=9b7c8633767f516ff9d48a8d6305b2a00a2101c82aa871b92e69086944f9f83e
   hashdiff (1.2.1) sha256=9c079dbc513dfc8833ab59c0c2d8f230fa28499cc5efb4b8dd276cf931457cd1
   i18n (1.15.2) sha256=00f9eb62412fe593b2a65a97daa75300d37abb8f7202ec748e94b6d46a9dd1b5
@@ -350,13 +350,13 @@ CHECKSUMS
   rubydex (0.2.7-x86_64-darwin) sha256=b002b259d118ac69de44470eff1597143318402c45630c47371f9542631447dc
   rubydex (0.2.7-x86_64-linux) sha256=dacfade9fa42ce4469618da6dac07e69d5f3ac6a313b4caced5234c8f052419a
   securerandom (0.4.1) sha256=cc5193d414a4341b6e225f0cb4446aceca8e50d5e1888743fac16987638ea0b1
-  simplecov (1.2.0) sha256=ea6acd05eece5a41990e2a5171c57d15700d329326c7666c85ee8c6a0dd0977e
-  sorbet (0.6.13485) sha256=b885d6a2fcde57bc46c3cdd597b9014b82619dee0f811a6fdf36f57c8f82c380
-  sorbet-runtime (0.6.13485) sha256=2982504e662eb424e515b3aa1c8139070451a014b6c1af2302250ed82495b4cc
-  sorbet-static (0.6.13485-aarch64-linux) sha256=5d802793633363442f189615fdb6c6d1be726b402d78a3d63eab96ca74b98d40
-  sorbet-static (0.6.13485-universal-darwin) sha256=6c7c4551872d556b37bf1f1a3495509b9fd9479b4a080bd57f9c5db0e8116658
-  sorbet-static (0.6.13485-x86_64-linux) sha256=e22d88df0bba5a97e664a329a2212ea59e6a2020626597a162c60c5ddfb4f9b4
-  sorbet-static-and-runtime (0.6.13485) sha256=b893346f9e1a244133071ad3c3d06b8ddf70c1b8246bb594c9aaa5cfc778df5f
+  simplecov (1.3.0) sha256=d9886307863c1ead47657dcbed869bfffd82318808b09014d8f0ff77dcfe7492
+  sorbet (0.6.13498) sha256=cb5279f6a9dbfc8d526bc9fb71d05020afb8043c40708e4aff2244ba329ce224
+  sorbet-runtime (0.6.13498) sha256=2da4627f9341a1fc6e4148cc891989b7b108106c206c46ca69940e10a21e9133
+  sorbet-static (0.6.13498-aarch64-linux) sha256=cbee732c49379d38029f295b45edaeb5757ab180d308d8383dc79f03fd4991be
+  sorbet-static (0.6.13498-universal-darwin) sha256=4cc97aa0da3dd175b8278e1617954d6dd9ba1f5aeb62981f21616b9ec791fb75
+  sorbet-static (0.6.13498-x86_64-linux) sha256=75d02e8af7d6c1081d4693e2ebefe679760327f1304377519970784faf9f913d
+  sorbet-static-and-runtime (0.6.13498) sha256=5f5686869dceae893b4171b05e3db159fe12f1aadf04aa8c2bf9dfa3edc0d902
   spoom (1.8.3) sha256=32871fa189bbfa49cf557a50f819f23cc9a6ceefd0346caa7a6adc193becd5dd
   tapioca (0.19.2) sha256=938731b07811aee8d23871b1aee8861d464fbaf2cfffbf79a62b0c869a5120ec
   thor (1.5.0) sha256=e3a9e55fe857e44859ce104a84675ab6e8cd59c650a49106a05f55f136425e73

data/docs/federation.md

@@ -129,11 +129,13 @@ your resolvers run, which is the whole point.
 
 In rspec that's the [`graphql: :router`](testing.md#a-federated-graph--graphql-router)
 tag and there is nothing to pass — the tag builds it, once for the suite. It finds
-the supergraph where you have already said it is: `Testing.config.router =
-{ supergraph: … }` if you named one there, else the schema a
+the supergraph where you have already said it is: the schema a
 [graph](getting_started.md#more-than-one-schema) declares when that schema is
-composed, else the committed dump when *that* is. Two graphs may name one
-supergraph; two naming different ones is refused rather than picked between.
+composed, else `Testing.config.router = { supergraph: … }` if you named one
+there, else the committed dump when *that* is, else the dump your own client was
+built from (`GraphWeaver.new("supergraph.graphql")` keeps its path). Two graphs
+may name one supergraph; two naming different ones is refused rather than picked
+between.
 Outside rspec, build it yourself:
 
 ```ruby
@@ -406,14 +408,12 @@ client distinct from the one the app uses to reach the gateway from outside:
 
 ```ruby
 # config/initializers/graph_weaver.rb — beside GraphWeaver.graph :reviews,
-# whose client is "Reviews::Schema"
-PLATFORM = GraphWeaver.new(ENV.fetch("PLATFORM_GRAPHQL_URL"))
-
+# whose client is Reviews::Schema
 GraphWeaver.graph :platform do
   schema    "app/graphql/supergraph.graphql"
   queries   "app/graphql/platform/queries"
   output    "app/graphql/platform/generated"
-  client    "PLATFORM"
+  client    GraphWeaver.new(ENV.fetch("PLATFORM_GRAPHQL_URL"))
   namespace "Platform"
 end
 ```

data/docs/generated_modules.md

@@ -38,7 +38,7 @@ module PersonQuery
     const :person, T.nilable(Person)
   end
 
-  extend GraphWeaver::QueryModule # client / client= (see below)
+  extend GraphWeaver::QueryModule # client (see below)
   def self.execute(id:, client: nil)    # -> GraphWeaver::Response[Result]
   def self.execute!(id:, client: nil)   # -> Result, or raises QueryError
 
@@ -543,21 +543,20 @@ bodies. Every form above, and every error it raises, is a named example in
 
 A client is anything satisfying the [execute contract](transports.md) — a
 `GraphWeaver::Client`, a transport, a `Retry`, a live schema class, a fake.
-Resolution is per call (`client:`) → per module → baked constant →
-`GraphWeaver.client`; the canonical list is in
-[transports](transports.md#client-resolution). Generate *without* a baked
-constant when you want modules to follow the app default (`GraphWeaver.client =`
-in an initializer). A baked one is no reason a module escapes
-[testing's `graphql:` tag](testing.md), which is exactly the instruction to
-replace the client generation chose; what the *example* says still wins.
-
-`client`/`client=` live in the gem (`GraphWeaver::QueryModule`, extended by every
-generated module). A baked constant is emitted as a private `DEFAULT_CLIENT`,
-resolved on first use so a module can load before the initializer that builds its
-client. A module generated from a
-[declared graph](getting_started.md#more-than-one-schema) also carries a private
-`GRAPH` naming it — so with two graphs, `graphql: :fake` fabricates each module's
-own schema instead of having to be told which one you meant, and it is the
+A module knows which graph it belongs to, and the graph knows how to reach it:
+resolution is per call (`client:`) → a test mode's stand-in → the client its
+[graph](getting_started.md#more-than-one-schema) names → `GraphWeaver.client`;
+the canonical list is in [transports](transports.md#client-resolution). There is
+no setter — `MyQuery.client` reads back what the module would execute through,
+and a [parsed](#dynamic-mode) module, which has no graph, runs
+against whatever parsed it. A graph naming its own client is no reason a module
+escapes [testing's `graphql:` tag](testing.md), which is exactly the instruction
+to replace it; what the *example* says still wins.
+
+`client` lives in the gem (`GraphWeaver::QueryModule`, extended by every
+generated module). A generated file says nothing about transport — only a private
+`GRAPH` naming its graph, which is also how `graphql: :fake` fabricates each
+module's own schema with two graphs in play, and the
 `:graph` on every [instrumentation event](logging.md#the-payload) the module's
 `execute` produces.
 
@@ -679,8 +678,9 @@ spot a *schema* change for you — `schema:diff`, `schema:refresh`, `queries:che
 ### Loading what it wrote
 
 In Rails, loading is automatic — the Railtie requires every generated file at
-boot from a `to_prepare` block, after your initializers and after any
-registrations of your own in one. Elsewhere it's explicit, factory_bot-style:
+the end of boot, after your initializers and after any registrations of your own
+in a `to_prepare` block, and again after each development reload. Elsewhere it's
+explicit, factory_bot-style:
 `GraphWeaver.load_generated!` requires every file under `generated_paths`.
 
 **Outside Rails, four things have to agree**, and nothing wires them together for
@@ -690,8 +690,8 @@ you — a script that generates its own modules sets all four:
 2. `generated_paths` — where it writes, and where `load_generated!` reads. Point
    them at the same directory or generation is invisible.
 3. the call above, before the first `execute` — nothing else requires the files.
-4. `GraphWeaver.client =` — a module generated without a baked
-   [`client:`](#clients) has none of its own.
+4. `GraphWeaver.client =` — a module belonging to no declared graph has no
+   other [client](#clients) to reach for.
 
 Miss (3) and the script gets a `NameError` for its own module; miss (4) and it
 gets `PersonQuery: client must respond to #execute(query, variables:), got
@@ -723,9 +723,16 @@ form: parse and execute in one call, no module kept. In development
 `client.load_queries!` parses every query file into modules with the same names
 generation would use.
 
+A parsed module **runs against whatever parsed it** — `client.parse(query)` and
+`load_queries!` bind the client they came from, and `GraphWeaver.parse(client:)`
+says it outright. That is a property of parsing, not a slot you can set later:
+it generates no file, so it has no graph to read a client off, and a per-call
+`client:` still wins over it.
+
 In an app with [more than one graph](getting_started.md#more-than-one-schema), a
 parsed module belongs to one of them — that is what a `graphql:` tag runs it
-against, the same thing generation bakes into a file. It is read off the schema
+against and whose `client` it reaches for, the same thing generation writes into
+a file. It is read off the schema
 you parsed against when a graph runs that class in-process; say it outright
 otherwise:
 

data/docs/getting_started.md

@@ -52,8 +52,8 @@ would drop the source url it records; delete it and re-run to re-introspect.
 What it wrote:
 
 - **`config/initializers/graph_weaver.rb`.** `GraphWeaver.client =` is the
-  load-bearing line: generated modules without a baked transport resolve to it
-  at execute time (the full
+  load-bearing line: generated modules belonging to no declared graph resolve to
+  it at execute time (the full
   [resolution order](transports.md#client-resolution)). Custom
   scalars/enums/type helpers register here too — the rake tasks bake them into
   generated source, so they have to run first ([scalars](scalars.md)):
@@ -99,8 +99,9 @@ What it wrote:
 
 Rake needs no wiring: in Rails the `graph_weaver:*` tasks register themselves and
 depend on `:environment`, so your initializer runs first. The generated modules
-load at boot from a `to_prepare` block, so a helper or enum you registered is
-already in place when the file that names it loads.
+load at the end of boot, after your initializers and after any `to_prepare`
+block of yours, so a helper or enum you registered is already in place when the
+file that names it loads.
 
 All of that describes **one** schema, which is the usual case; an app with a
 second one declares each as a graph ([more than one
@@ -428,7 +429,7 @@ plus `register_scalar`, `register_enum` and `extend_type`).
 | `schema` | a graphql-ruby schema class, a [`Client`](transports.md), a path to a dump, SDL, or a lambda returning one |
 | `queries` | a directory, or a list of them — the `.graphql` files this graph generates from |
 | `output` | one directory — where this graph's generated Ruby is written |
-| `client` | a constant, or its name — what this graph's modules execute against |
+| `client` | what this graph's modules execute against — a client, or the name of the constant holding one |
 | `namespace` | a constant, or its name — what every constant this graph generates nests under |
 | `types_module` | a constant name for the shared types module (default: `GraphQLTypes`, under `namespace`) |
 
@@ -447,14 +448,14 @@ GraphWeaver.graph :app do
 end
 ```
 
-**`client` names a constant, not a url** — its value is spelled into every module
-this graph generates and resolved the first time one of them executes, so it has
-to be something generated source can write down. Build the client wherever you
-like (`GITHUB = GraphWeaver.new(url, auth: …)`) and put the constant holding it
-here. A graph with no `client` generates modules that fall back to
-`GraphWeaver.client`, the app default. `schema "x"` sets and a bare `schema`
-reads back; there is no `schema = "x"` form, since the block is `instance_eval`'d
-and that would be a local variable that silently does nothing.
+**`client` is where this graph's endpoint lives** — its modules say which graph
+they belong to and nothing about transport, so they read it when they execute.
+A graph with no `client` falls back to `GraphWeaver.client`, the app default.
+Name the object (`client GraphWeaver.new(url, auth: …)`) or, when the constant
+holding it is defined later than the graph block, its name (`client "GITHUB"`),
+which is resolved on first use. `schema "x"` sets and a bare `schema` reads
+back; there is no `schema = "x"` form, since the block is `instance_eval`'d and
+that would be a local variable that silently does nothing.
 
 **`namespace` nests everything that graph generates** — `person.graphql` becomes
 `Billing::PersonQuery` ([naming](generated_modules.md#naming)). Constants are

data/docs/testing.md

@@ -36,8 +36,8 @@ it "sends the caller tag",    graphql: :wire do … end
 There is nothing else to set up: each mode works out what to run against per
 graph, and [refuses rather than guessing](#nothing-to-configure). The tag
 installs a stand-in per graph, and every generated module of that graph runs
-against it — including one generated *with* a baked `client:`, since that
-constant is exactly what the tag means to replace. `rspec --tag graphql:router`
+against it — including one whose graph names a `client` of its own, since that
+is exactly what the tag means to replace. `rspec --tag graphql:router`
 runs one mode's examples.
 
 **Every example has exactly one mode.** An untagged one takes
@@ -50,7 +50,8 @@ whatever the example did to it, so building your own client is a plain
 assignment: `before { GraphWeaver.client = GraphWeaver::Testing::Failure.throttled }`.
 Do both at once and **the tag wins**: the assignment reads back while the modules
 keep using the mode. Two things do step out of a tag — a per-call `client:`, and
-`DashboardQuery.client =` on the module itself
+a module [parsed](generated_modules.md#dynamic-mode) from a client of its own,
+which runs against that client
 ([client resolution](transports.md#client-resolution) has the full order).
 
 **The half `:fake` can't reach** is refusal. It fabricates a shape-correct
@@ -340,10 +341,10 @@ suite. The tag adds one stub per endpoint and takes each back after the example
 it never disables net connections on your behalf, and never resets stubs it
 didn't make.
 
-**Every endpoint an example can reach is served**, one per graph: the client each
-[declared graph](getting_started.md#more-than-one-schema) bakes into its modules
-with `client:`, or `GraphWeaver.client` for a graph that bakes none — so a
-billing module posts to billing's url and is answered by billing's schema. What
+**Every endpoint an example can reach is served**, one per graph: the `client`
+each [declared graph](getting_started.md#more-than-one-schema) names, or
+`GraphWeaver.client` for a graph naming none — so a billing module posts to
+billing's url and is answered by billing's schema. What
 sits behind each is **what that graph is**, in descending faithfulness: that
 graph's [router](#a-federated-graph--graphql-router) when it is in a composed
 supergraph, its [live schema class](#real-resolvers--graphql-in_process) when it
@@ -352,8 +353,8 @@ that is a pure *client* of someone else's API gets a schema-correct server
 without writing one. A graph with no schema at all is refused, **by `:wire`'s own
 name** — the one fallback the other tags have and this one can't use is your
 client's own schema, since reading it means introspecting the endpoint `:wire`
-has just stubbed. Commit a dump, or set `config.schema`. A graph whose baked
-client posts nowhere is refused by name too.
+has just stubbed. Commit a dump, or set `config.schema`. A graph whose `client`
+posts nowhere is refused by name too.
 
 **It says which, on the logger** — the choice is the one thing this tag makes for
 you, and it is invisible from inside the example. One line per endpoint, at
@@ -542,11 +543,13 @@ rather than guessing**:
   [maps subgraphs](federation.md#which-schema-serves-which-subgraph).
 - **`:router`** plans against the composed supergraph **that graph** names, else
   `config.router = { supergraph: … }`, else the committed dump when *that*
-  carries `@join__*` markers — which for a federated app is usually no config at
-  all. A graph that is in no supergraph is refused **by name**, rather than
-  planned against another graph's. A client can't stand in for one: a client's
-  schema is the API schema the router serves, with the `@join__*` routing table
-  stripped out. Subgraphs are derived either way.
+  carries `@join__*` markers, else the dump your own client was built from
+  (`GraphWeaver.new("supergraph.graphql")`) — which for a federated app is
+  usually no config at all. A graph that is in no supergraph is refused **by
+  name**, rather than planned against another graph's. A client's *schema* can't
+  stand in for one — it is the API schema the router serves, with the `@join__*`
+  routing table stripped out — but the file it was read from carries the table.
+  Subgraphs are derived either way.
 
 So configure only to override a derivation, or to tune fabricated values — in the
 same file as the require, since support files load in sorted order and one naming

data/docs/transports.md

@@ -37,8 +37,8 @@ applied (exposed as `client.transport`), the schema introspected lazily, and
 
 They combine, so the whole thing is still one call —
 `GraphWeaver.new(url, transport: :faraday, retries: 2) { |conn| conn.response :logger }`.
-To wire generated modules that don't bake a client, make it the app's default:
-`GraphWeaver.client = github`.
+To wire generated modules belonging to no declared graph, make it the app's
+default: `GraphWeaver.client = github`.
 
 ## What fills the client slot
 
@@ -202,22 +202,29 @@ APM payload gets ([errors](errors.md)).
 
 ## Client resolution
 
+A module knows which graph it belongs to, and the graph knows how to reach it.
 The canonical order — how a generated module finds its client (each slot takes a
 `Client` or any bare transport/fake):
 
 1. per call: `execute(client: some_client, ...)` — a kwarg like the variables, and
    a name no GraphQL variable is allowed to take
-2. per module: `MyQuery.client = something`
-3. a test mode's stand-in: under `graphql: :fake` / `:in_process` / `:router`,
+2. a test mode's stand-in: under `graphql: :fake` / `:in_process` / `:router`,
    built from the graph this module was generated from
-4. baked constant: `Codegen.generate(..., client: "MyApi::CLIENT")` — the
-   constant's *name*, not the object, because generated source spells it
-5. the app default: `GraphWeaver.client=`
+3. the client its [graph](getting_started.md#more-than-one-schema) names
+4. the app default: `GraphWeaver.client=`
 
-The mode replaces what codegen baked in, not what your example said — 1 and 2
-still win. Nothing set anywhere raises, naming the two you'd usually reach for:
+The mode replaces what the graph says, not what your example said — 1 still
+wins. Nothing set anywhere raises, naming the two you'd usually reach for:
 `no client configured — set GraphWeaver.client= or pass a client`.
 
+**A [parsed](generated_modules.md#dynamic-mode) module isn't in that list**: it generates no
+file, so it has no graph, and it runs against whatever parsed it —
+`client.parse(query)`, `load_queries!`, or `GraphWeaver.parse(client:)`. That
+binding sits directly under the per-call `client:`, above even a test mode's
+stand-in, and is the only one there is: `MyQuery.client` reads back what a
+module would execute through, but there is no setter for it. A module's client
+comes from its graph, its parser, or the call.
+
 ## Retries
 
 A url client retries when you give it a count; the rest of the options sit beside

data/docs/upgrading.md

@@ -1,10 +1,11 @@
 # Upgrading
 
 [Regenerate](#regenerate-on-every-upgrade) whichever version you're on, then read
-the one section that is yours: from [0.7.0](#upgrading-from-070) or from
-[0.6.1](#upgrading-from-061). Coming from 0.6.0 or older, the path is that
-version's own upgrade notes — read them at the tag they shipped under
-(`git show v0.7.1:docs/upgrading.md`), then this page from 0.6.1 down.
+the one section that is yours: from [0.7.1](#upgrading-from-071), from
+[0.7.0](#upgrading-from-070) or from [0.6.1](#upgrading-from-061). Coming from
+0.6.0 or older, the path is that version's own upgrade notes — read them at the
+tag they shipped under (`git show v0.7.1:docs/upgrading.md`), then this page from
+0.6.1 down.
 
 ## Regenerate on every upgrade
 
@@ -22,6 +23,28 @@ That's the reminder working, not a false alarm. Generation is deterministic, so
 the diff is exactly what the new version emits differently and nothing else —
 worth reading rather than rubber-stamping.
 
+## Upgrading from 0.7.1
+
+A patch release, and one change with a shape: a generated module no longer
+carries a client of its own — the graph it belongs to resolves one. Read the
+left column and skip what isn't yours; the [changelog](../CHANGELOG.md) says why
+each one moved.
+
+| applies if you… | what changed |
+|---|---|
+| call `generate!`, `verify_generated!`, `Codegen.new` or `Codegen.generate` yourself — `grep -rn "client:" config lib Rakefile` | the `client:` kwarg is gone, and the call raises `unknown keyword: :client`. Say it once on the graph (`client` in a `GraphWeaver.graph` block), or as the app default (`GraphWeaver.client =`) for modules in no declared graph. `Graph#client` answers that object now, not the name of the constant holding it |
+| assign a generated module's client — `grep -rn "\.client *=" app config lib` (a hit on `GraphWeaver.client =` is the app default, and still fine) | the writer is private, and `MyQuery.client = …` raises `NoMethodError`. A module's client comes from its graph, from `client:` on the call, or — for a module you parsed — from `GraphWeaver.parse(client:)`, which `client.parse` and `load_queries!` already pass |
+
+Then regenerate, and the gate:
+
+```sh
+# generated files no longer carry a DEFAULT_CLIENT
+rake graph_weaver:generate
+
+# red while any checked-in file is still what 0.7.1 wrote
+rake graph_weaver:verify
+```
+
 ## Upgrading from 0.7.0
 
 A patch release of fixes, and a typical app ticks none of these. Read the left
@@ -167,7 +190,7 @@ only one here that shows up in production rather than in your code.
 - **A `graphql:` tag reaches a module generated with `client:`.** The baked client
   used to sit above the slot a tag swaps, so a bound module ran against its real
   endpoint under `graphql: :fake`. **If a spec relied on that**, pass `client:` on
-  the call, set `MyQuery.client =`, or tag the example `graphql: :live`.
+  the call, or tag the example `graphql: :live`.
 - **`config.context`, `config.schema` and `config.router` are suite setup.**
   Setting any of the three once an example is running refuses, naming the
   per-example helper (`graphql_context`, `graphql_fake(schema:)`,

data/examples/github/generated/star_mutation.rb

@@ -1,7 +1,7 @@
 # typed: strict
 # frozen_string_literal: true
 
-# Generated by GraphWeaver 0.7.0 — do not edit.
+# Generated by GraphWeaver 0.7.3 — do not edit.
 
 module StarMutation
   extend T::Sig
@@ -79,11 +79,11 @@ module StarMutation
     end
   end
 
-  # client / client= — see GraphWeaver::QueryModule
+  # client — see GraphWeaver::QueryModule
   extend GraphWeaver::QueryModule
 
-  # the graph this module was generated from — what a test mode builds
-  # its stand-in client from
+  # the graph this module was generated from — whose client it runs
+  # against, and what a test mode builds its stand-in from
   GRAPH = T.let(:github, Symbol)
   private_constant :GRAPH
 

data/examples/github/generated/stargazers_query.rb

@@ -1,7 +1,7 @@
 # typed: strict
 # frozen_string_literal: true
 
-# Generated by GraphWeaver 0.7.0 — do not edit.
+# Generated by GraphWeaver 0.7.3 — do not edit.
 
 require "time"
 
@@ -183,11 +183,11 @@ module StargazersQuery
     end
   end
 
-  # client / client= — see GraphWeaver::QueryModule
+  # client — see GraphWeaver::QueryModule
   extend GraphWeaver::QueryModule
 
-  # the graph this module was generated from — what a test mode builds
-  # its stand-in client from
+  # the graph this module was generated from — whose client it runs
+  # against, and what a test mode builds its stand-in from
   GRAPH = T.let(:github, Symbol)
   private_constant :GRAPH
 

data/examples/github/generated/starred_query.rb

@@ -1,7 +1,7 @@
 # typed: strict
 # frozen_string_literal: true
 
-# Generated by GraphWeaver 0.7.0 — do not edit.
+# Generated by GraphWeaver 0.7.3 — do not edit.
 
 module StarredQuery
   extend T::Sig
@@ -103,11 +103,11 @@ module StarredQuery
     end
   end
 
-  # client / client= — see GraphWeaver::QueryModule
+  # client — see GraphWeaver::QueryModule
   extend GraphWeaver::QueryModule
 
-  # the graph this module was generated from — what a test mode builds
-  # its stand-in client from
+  # the graph this module was generated from — whose client it runs
+  # against, and what a test mode builds its stand-in from
   GRAPH = T.let(:github, Symbol)
   private_constant :GRAPH
 

data/lib/graph_weaver/client.rb

@@ -77,6 +77,10 @@ class GraphWeaver::Client
       # a live schema class doubles as an in-process transport; a loaded
       # dump has no resolvers, so it is type information only
       @schema = source.is_a?(Module) ? source : GraphWeaver::SchemaLoader.load(source)
+      # A supergraph's routing table lives in the file, not in the loaded
+      # schema, so the path is the only thing that can name one later. Told
+      # from SDL by its extension, as SchemaLoader tells it.
+      @schema_source = source if !source.is_a?(Module) && GraphWeaver::SchemaLoader.dump_path?(source)
 
       if context && !(source.is_a?(Module) && transport.nil?)
         # nothing would ever read it — a dump has no resolvers, and an
@@ -122,6 +126,10 @@ class GraphWeaver::Client
   # schema-dump clients (type information only).
   attr_reader :transport
 
+  # The dump this client's schema was read from, or nil for a url, a schema
+  # class, or inline SDL. What a graph named by this client is named by.
+  attr_reader :schema_source
+
   # transport, when this client must be able to execute
   private def transport!
     transport or raise GraphWeaver::Error,

data/lib/graph_weaver/codegen/emit.rb

@@ -456,22 +456,16 @@ class GraphWeaver::Codegen
     end
 
     def emit_execute(out, variables)
-      # client/client= carry no per-query types, so they live in the gem
-      out << "  # client / client= — see GraphWeaver::QueryModule"
+      # client carries no per-query types, so it lives in the gem
+      out << "  # client — see GraphWeaver::QueryModule"
       out << "  extend GraphWeaver::QueryModule"
       if @graph_name
         out << ""
-        out << "  # the graph this module was generated from — what a test mode builds"
-        out << "  # its stand-in client from"
+        out << "  # the graph this module was generated from — whose client it runs"
+        out << "  # against, and what a test mode builds its stand-in from"
         out << "  GRAPH = T.let(#{@graph_name.inspect}, Symbol)"
-        out << "  private_constant :GRAPH"
-      end
-      if @client_const
-        out << ""
-        out << "  # the baked default client, resolved on first use"
-        out << "  DEFAULT_CLIENT = T.let(-> { #{@client_const} }, T.proc.returns(T.untyped))"
         # QueryModule reads it with const_get, which privacy doesn't block
-        out << "  private_constant :DEFAULT_CLIENT"
+        out << "  private_constant :GRAPH"
       end
       out << ""