pub struct IndexGraphql {
pub backends: Vec<IndexBackend>,
}Expand description
WHICH GRAPHQL BACKENDS DRESS THIS DECLARATION — the graphql(…) block, or None where the
declaration named none.
§The word gates the SKIN and never the BONES
Without a block the RUST surface emits WHOLE: the doors, the packages, the evidence, the
selector and the Fusable binding are all there, and a pipeline
driven from Rust is missing nothing. What the word buys is one backend’s WIRE IMPLS over those
same types — the hand-written InputType / @oneOf / enum faces, and the registry entries the
SDL is read out of.
That is why a backend WORD is what the block holds rather than a bare graphql: the framework
renders through several, the types are backend-NEUTRAL, and each declared word adds one skin over
the one set of bones. The __<backend>_ ident prefix is what keeps two coexisting skins from
colliding, and it is reserved per backend for exactly this.
Fields§
§backends: Vec<IndexBackend>The backends this declaration named, in the order it wrote them.
A LIST rather than one, because the block is which skins, and a declaration that grows a
second word grows a second skin over the types it already had. EMPTY is the bare graphql
spelling, which names no backend and therefore dresses nothing — refused at the front end,
where the sentence can name the words on offer.
Implementations§
Source§impl IndexGraphql
impl IndexGraphql
Sourcepub fn of(kind: GraphqlKind) -> Self
pub fn of(kind: GraphqlKind) -> Self
A block naming ONE backend — the shape a declaration writing graphql(async_graphql) builds.
Sourcepub fn renders(&self, kind: GraphqlKind) -> bool
pub fn renders(&self, kind: GraphqlKind) -> bool
Whether this declaration named kind.
Sourcepub fn skin(&self, kind: GraphqlKind) -> Option<&IndexBackend>
pub fn skin(&self, kind: GraphqlKind) -> Option<&IndexBackend>
kind’s block, or None where this declaration named that backend nowhere.