Preview context kinds
The template playground previews a body under a chosen context source, its kind. Five kinds are table-shaped (table, landing table, staging table, staging notebook, test) and run the family builders documented in this reference: each keys its builder off a table you pick. Three more are not table-grained and build their own small contexts, documented below.
The ninth kind is sample, which is not a builder at all: it renders the curated fixture the family itself ships, keyed by the family. Every family that lists sample in the family index carries one, and for the families with no live strategy it is the only way to preview them.
Previewing a body under a kind its family does not accept still renders, and the kind-family-mismatch diagnostic says the context is a stand-in.
connection
Section titled “connection”The narrow connection identity, which is what this kind builds for a body that
needs to name a connection rather than configure one. The linked-service
templates need a wider connector shape, and they get it: picking a connection
for the adf-linked-service family routes to an allowlisted wide projection
instead of this identity, so the same kind serves both without either body
seeing a hollow context.
| Field | Type | Meaning |
|---|---|---|
connection.ulid | string | The connection’s identifier. |
connection.name | string | Display name. |
connection.connectionType | string | Connector type. |
connection.catalog / .defaultSchema | string? | Default catalog and schema, when set. |
project
Section titled “project”| Field | Type | Meaning |
|---|---|---|
project.ulid | string | The project’s identifier. |
project.name | string | Project name. |
project.projectType | string | The target-platform type the platform classifier reads. |
project.workspaceName | undefined | Emitted as a placeholder, currently always undefined. |
workflow
Section titled “workflow”The orchestration preview context: the same shape the workflow family documents, assembled from a workflow you pick. Custom SQL bodies pass through verbatim (macros are not expanded on this preview path), and activity dependency names come back empty: both are accepted preview-fidelity tradeoffs, and a Build resolves them fully.