Reference
@sushindustries/uiAn inline mention that carries a hover card with the target's own summary.
Props
| Prop | Type | Default | Does |
|---|---|---|---|
| referenceReferenceAn inline mention that carries a hover card: title, summary and meta for the thing it names, raised by CSS alone.@sushindustries/ui · content | ReferenceReferenceAn inline mention that carries a hover card: title, summary and meta for the thing it names, raised by CSS alone.@sushindustries/ui · content | - | The target, resolved by the caller. The card is built from this, never fetched. |
children | ReactNode | - |
Notes
referenceReferenceAn inline mention that carries a hover card: title, summary and meta for the thing it names, raised by CSS alone.@sushindustries/ui · content is never re-derived from children - the two are independent.
Passing children that don't match reference.title (calling it "the
pagination component" while linking a ReferenceReferenceAn inline mention that carries a hover card: title, summary and meta for the thing it names, raised by CSS alone.@sushindustries/ui · content titled "Pagination") is
legal and renders exactly that mismatch; nothing checks them against each
other.
Nesting a Ref inside another link, or inside another Ref, isn't
handled - anchors don't nest in valid HTML, and the browser's own parsing
behaviour decides which one wins, not this component.