Skip to content

test(ui): deepen Children parity (count/flatten)#44

Merged
monstercameron merged 1 commit into
masterfrom
react-parity/deepen-children
Jun 25, 2026
Merged

test(ui): deepen Children parity (count/flatten)#44
monstercameron merged 1 commit into
masterfrom
react-parity/deepen-children

Conversation

@monstercameron

Copy link
Copy Markdown
Owner

Deepens the ReactChildren port: count/flatten/filter across many input shapes (nil/single/flat/nested/mixed), deep-flatten order. All pass; no version bump.

🤖 Generated with Claude Code

Toward React-suite equivalency for the GWC-applicable ReactChildren subset
(count/flatten/filter — GWC has html.Children normalization, not the
Children.map/forEach/count API): count is 0 for nil/empty, 1 for a single
arrayless or sliced child, N for flat and deeply (2-3 level) nested structures,
nil is filtered, mixed kinds flatten; deep nesting flattens in document order.

All pass; no version bump.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@monstercameron monstercameron merged commit 1f3746e into master Jun 25, 2026
2 checks passed
@monstercameron monstercameron deleted the react-parity/deepen-children branch June 25, 2026 04:04
monstercameron pushed a commit that referenced this pull request Jul 6, 2026
#44)

The wasm backend now leads the console call with the message string when
it is non-empty (console.log(message, record)) so the message is readable
and matchable in devtools. But two test console stubs still captured
parseArgs[0] as the structured "entry"/"payload" — now the MESSAGE STRING
— so getLoggingTestRecord/findLoggingTestPayload called .Get("message")
on a string and panicked ("Value.Get on non-object"), failing the whole
logging wasm suite. Capture the LAST argument (always the record object)
instead.

The other #44 item (parallel-region wasm panic) is resolved: the
ParallelRegion wasm tests pass (the specific failure was fixed under #40).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants