woonki

Thank you for asking. I don't think this feature should affect the PPX V4 for now. I agree to move to milestone 10.2.

I'm not going to say that the error msg is kind or informative enough, but the object is not allowed to be updated basically. https://rescript-lang.org/docs/manual/latest/object#update The usage of `@set` is...

First of all, the inlined annotated type `{.. "name": string}` or `{"name": string}` is not inferred to the type `withName`. Those are not bounded to each other at all. As...

The jsx ppx is not activated if the jsx config(old or new) doesn't exist. Still not sure about making the v4 classic as default when the configuration about jsx doesn't...

Oh, sorry, I misunderstood. I thought we had an agreement. I'll hold this PR as a draft, but I'll ask the community about the V4 as default. It is worth...

This PR can be closed due to introducing #5661

I think if this PR with commit is merged https://github.com/rescript-lang/syntax/pull/586/commits/c59520c59f53554beb843da3410954cf80d70a67, it will point the right location of source code about unlabelled ref in forwardRef.

But I agree on the comment from @ryyppy, please don't use the React.forwardRef API if possible 😃

It is worth trying with `external` binding with a component written in js. ``` @react.component @module("./react/ErrorBoundary.jsx") external make: (~children: ...) => React.element = "default" ```

By the way, `ErrorBoundary` component is not an official React API. It is worth considering moving it to user space.