layoutLibraryNodeSource

What the padlock on a placed block needs to know about where that block came from (§3.2).

BY UUID, because that is what a reference stores — ids are meaningless across deployments. Sees soft-deleted nodes on purpose: "the original was deleted from your Library" is one of the five padlock states, and hiding trashed rows would report it as "no such node" instead. Returns null for a node that does not exist OR belongs to another product — the two must be indistinguishable, or a guessed uuid becomes a way to read another tenant's block names.

layoutLibraryNodeSource(
  uuid: String!
): LayoutLibraryNodeSource

Arguments

layoutLibraryNodeSource.uuid ● String! non-null scalar

Type

LayoutLibraryNodeSource object

What the BUILDER needs about a referenced Library node: the facts libraryLinkState() decides the padlock from, and the body itself.

ONE LOOKUP FOR THREE CONSUMERS, deliberately. The padlock reads the flags, the canvas island renders properties, and detach() materialises from the same properties — so the thing an author sees and the thing detaching produces cannot disagree, which is what detach always claimed and could not guarantee while it read a dependency nobody populated.

NONE OF IT IS ON A PUBLISHED PAYLOAD, and does not need to be. Every published render flattens its references server-side, so no published surface ever meets a LIBRARY_REF. This query is @guard-ed, which is fine for exactly that reason — unlike the Drop Down options fallback, which was guarded AND relied on by published forms until #7389 found it.

A block that has been DETACHED still queries this for its padlock state, and pulls a properties it will not render. One body, on a builder request, to keep a single hook serving every case.