Skip to content

Commit 764dd5a

Browse files
committed
docs: document string alignment in renderer spec
1 parent b8fa9e7 commit 764dd5a

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

specs/renderer-spec.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -633,9 +633,9 @@ The `open()` constructor currently accepts the following property groups in its
633633
`props` parameter:
634634

635635
- **`layout`** — sizing (width and height, specified via sizing helpers),
636-
padding (per-side), alignment (currently numeric enum values, with a planned
637-
transition to string literals), direction (top-to-bottom or left-to-right),
638-
and gap
636+
padding (per-side), alignment (`alignX`: `"left"` | `"center"` | `"right"`;
637+
`alignY`: `"top"` | `"center"` | `"bottom"`, defaulting to left/top when
638+
omitted), direction (top-to-bottom or left-to-right), and gap
639639
- **`border`** — per-side border widths and border color
640640
- **`cornerRadius`** — per-corner radius values, producing rounded box-drawing
641641
characters
@@ -649,8 +649,7 @@ The `text()` constructor currently accepts: `color`, `fontSize`,
649649
`underline`, `strikethrough`).
650650

651651
These property groups represent the current implementation surface. New groups
652-
and fields have been added incrementally and more may follow. Alignment values
653-
are expected to transition from numeric to string-literal form.
652+
and fields have been added incrementally and more may follow.
654653

655654
**Border width and layout interaction.** In the underlying layout engine (Clay),
656655
border configuration does not affect layout computation. This is Clay's intended

0 commit comments

Comments
 (0)