Motivation
The Clay error handler in clayterm.c currently silently swallows all errors:
static void clay_error(Clay_ErrorData err) { (void)err; }This means duplicate IDs, capacity overflows, and other Clay diagnostics are invisible to callers. These should be surfaced in the render result so callers can detect and respond to layout issues.
Approach
Add an errors/warnings field to RenderResult and populate it from a Clay error handler that collects errors during the render transaction.
Motivation
The Clay error handler in
clayterm.ccurrently silently swallows all errors:This means duplicate IDs, capacity overflows, and other Clay diagnostics are invisible to callers. These should be surfaced in the render result so callers can detect and respond to layout issues.
Approach
Add an errors/warnings field to
RenderResultand populate it from a Clay error handler that collects errors during the render transaction.