uploadLayoutLibraryNodeThumbnail
Store the thumbnail the BUILDER captured of a node it just saved (§7).
The image is taken in the browser, from the canvas the author is looking at, because a thumbnail is a picture of LAYOUT and layout only exists once a real engine has measured fonts and wrapped text. So only a save made through the builder produces one — a node written by a backfill or a cross-instance clone has none, and the grid falls back to rendering it live, which it does for every node today.
FIRE AND FORGET from the client: the capture runs after the save has already succeeded and its failure is never surfaced, so a node is always saved whether or not its picture is.
uploadLayoutLibraryNodeThumbnail(
id: ID!
image: Upload!
): LayoutLibraryItem
Arguments
uploadLayoutLibraryNodeThumbnail.id ● ID! non-null scalar
uploadLayoutLibraryNodeThumbnail.image ● Upload! non-null scalar
Type
LayoutLibraryItem object
A node in the unified Layout Library.
The GraphQL NAME is unchanged on purpose. This type, its inputs and its mutations are called
LayoutLibraryItem across the front end, and the shape the client sees is the same shape —
so repointing the model is a backend move rather than a coordinated rename of both halves.
item_type_id keeps its wire name for the same reason and is mapped to the node_type_id
column; the VALUES are the same enum.
categories is retired (§2.5): folders do its one job now, and the node table has no such column.


