Fleet-Ops
Every resource view registry Fleet-Ops declares — the registry names for each table and details view, where each is wired in the Fleet-Ops source, and the built-in ids to place your items against.
Fleet-Ops Registries
Fleet-Ops (@fleetbase/fleetops-engine, from 0.6.71) declares registries for 25 resources. Every name starts with fleet-ops: and follows fleet-ops:<resource>:<surface>:<slot>.
The table lists each resource and the source file that wires it up. Open a resource below for its registry names and built-in ids.
Resources
Overview
Every resource view registry the built-in engines declare — one page per engine, with each resource's registry names, built-in ids and a link to the source that wires it.
Storefront
Every resource view registry Storefront declares — the registry names for each table and details view, where each is wired in the Storefront source, and the built-in ids to place your items against.