RelationshipList

<caos-relationship-list>

an object’s child relationships, with the field behind each and what a delete does to it

May be placed on a page inside an app and a record page.

Inputs

Name	Attribute	Description	Type	Default	Required
relationships	property only	What points here: { name, childObject, field, onDelete?, count? }[]. onDelete absent ⇒ NOT STATED, which is drawn as “not stated” and never guessed. count absent ⇒ not counted, which is not the same as none.	json	empty list	Optional
linkable	linkable, markup only	Make the object names pressable, raising caos-relationship-open. Off by default, because a link to somewhere the host has not wired is worse than plain text.	boolean	false	Optional
emptyText	empty-text, markup only	What to say when nothing points here. “Nothing points at this object” is a real and useful answer, so it is stated rather than left as a blank table.	text	Nothing points at this object.	Optional
sortKey	sort-key, markup only	Which column orders the rows.	text — one of childObject, name, field, onDelete, count	childObject	Optional
sortDirection	sort-direction, markup only	Which way. An uncounted relationship sorts last in both directions.	text — one of asc, desc	asc	Optional

Events

Name	When it fires	What it carries
caos-relationship-open	An object name is pressed, with linkable set.	{ object }.

Slots

Not documented yet — this piece has not said.

Styling hooks

Not documented yet — this piece has not said.

Methods

Not documented yet — this piece has not said.

Readable state

Name	Type	What it tells you
cascading	CaosRelationship[]	The relationships that would take records with this one. Read it to build a delete warning without re-deciding which behaviours are dangerous.
ordered	CaosRelationship[]	The relationships in the order they are shown.

Styling parts

Part	Which piece of it	When it is there
::part(list)	The outer column.	Always
::part(summary)	The count line, including how many would cascade.	Always
::part(table)	The composed data table.	Always
::part(object-link)	A pressable object name.	linkable is set.
::part(behaviour)	The on-delete cell.	Always
::part(count)	The record-count cell.	Always

When to use it

Before changing or deleting something, when the question is what ELSE depends on it. It is the reverse view of a lookup: not what this points at, but what points here.

What to use instead

• ObjectFieldExplorer — the question is what is ON this object rather than what points at it.
• DataTable — the rows are related RECORDS being listed, not the relationships themselves.

Accessibility

The summary is a role="status" live region and names the cascading count in words as well as in red, so “four of these would delete records with this one” is heard rather than only seen. Each delete behaviour is a sentence, not a vocabulary word, so a reader who does not already know what “cascade” means is not left to guess at the most consequential cell on the screen. Object names are <button> elements with an accessible name reading “Open