ppx: support "custom children" in uppercase components without having to wrap in array literal

[jchavarri]

Fixes #822.

The breaking change is for uppercase components that were introspecting with React.Children. After the change, these components would need to run children through React.array.

It allows to write:

<Test> {Test.name: "foo"} {name: "bar"} </Test>

besides the already possible:

<Test> [|{Test.name: "foo"}, {name: "bar"}|] </Test>

[anmonteiro]

I think this make sense.

I wonder if we should mention this difference between uppercase / lowercase components in our documentation.

[jchavarri]

@davesnx what are your thoughts on this?

I wonder if we should mention this difference between uppercase / lowercase components in our documentation.

@anmonteiro We do mention something already:

• https://reasonml.github.io/docs/en/jsx#capitalized-tag
• https://reasonml.github.io/docs/en/jsx#uncapitalized-tag

Do you mean to expand on that?

[anmonteiro]

@anmonteiro We do mention something already:

• https://reasonml.github.io/docs/en/jsx#capitalized-tag
• https://reasonml.github.io/docs/en/jsx#uncapitalized-tag

Do you mean to expand on that?

Right, I wonder if we should mention that these are no longer wrapped in array, or if it's OK just to document it in the changelog.

[davesnx]

Looks like a great idea, uppercase components supporting any children looks nice

[davesnx]

I wonder if you can add the test case for a fragment (which is a list on the parsetree) which avoids the wrapping.

<Test> <div>{React.string("HI")}<div/> <div>{React.string("HI")}<div/> </Test>

[anmonteiro]

merging this as discussed in https://ahrefs.slack.com/archives/C01RF16D2LA/p1732103117043289

let's revert if anyone disagrees.