Better type checking?

[AndiLavera]

https://github.com/facebook/react-strict-dom/blob/05226645531de66ae8d0f06c48c10e0526dfd438/packages/react-strict-dom/src/types/StrictReactDOMProps.js#L244-L280

Is there anything that could be done at this time to improve existing type definitions? Or, is type checking blocked by something else?

The onClick has a definition. Would PR's adding additional types be accepted? Is there a recommended starting place or really any $FlowFixMe that isn't dependent on other unimplemented types?

[yaminyassin]

I took a pass at this in #504. It replaces the $FlowFixMe event props on the StrictReactDOM* types with real payload types.

The handlers split into two groups:

• Ones the native factories re-synthesize (onChange, onInput, onClick, onKeyDown, onLoad, onError) get concrete payloads, so e.g. onChange hands you { type, target: { value } } and a typo on a field is a Flow error at the call site.
• Ones whose runtime shape is platform-defined (most pointer/mouse/touch/clipboard events) use a shared StrictOpaqueEventHandler. That still passes the event through, but the param is unknown instead of any, so it forces a narrow before use rather than silently typing clean.

On your "recommended starting place" question: the event props were a good first target because most of them are not blocked by other unimplemented types.