pub struct ArtifactBytes { /* private fields */ }Expand description
The wire field one artifact position’s data ask mints.
§It carries a NAME and nothing else, and the absent name is the DEFAULT
<domain-word>Data — thumb → thumbData — in the framework’s own camelCase, resolved at the
wire face where that rule has its one home. The alternative was resolving it in the front end and
storing a string, which would put a second authority on what a client sees beside
emit::wire::wire_member; the two would then be free to disagree about a word like key_frame.
So None is nothing was written rather than nothing is known, exactly as
Graphql::output’s empty rename is.
Implementations§
Source§impl ArtifactBytes
impl ArtifactBytes
Sourcepub const fn asked() -> Self
pub const fn asked() -> Self
The BARE ask — the data form, whose field is named at the face.
Written out rather than reached through Default, because the ask with no name is a state
this type has and not the absence of one: a reader of ArtifactBytes::default() would have to
go and look up which of the two forms it stands for.
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
The name a declaration wrote, or None where the default stands.
Verbatim, and never camelCased: a name a declaration CHOSE is that declaration’s, and applying
the backend’s rename rule to it would be this framework overriding the choice. The same fork
emit::wire::wire_field makes for a column’s own rename, one face over.
Sourcepub const fn require(self) -> Self
pub const fn require(self) -> Self
The same ask, marked NON-NULL — the data(required) form.
A consuming builder rather than a fourth constructor, because required is orthogonal to the two forms above: it composes with the bare ask and with the named one alike, and a constructor per combination is four names for two facts.