Wesley Wigham
Wesley Wigham
@ericanderson That's the plan. (I mean, technically it was a bug report a long time ago that we closed as "fixed" even though it was only half-fixed)
By `defaultProps` do you mean the intrinsic props?
... _maybe_. Even with localized types looked up from the signatuers, we still have to make assumptions about how the custom ctor/sfc is effectively built, because there's actually two calls...
Yes, technically. You can already define such a type in TS, it just isn't terribly useful since every JSXExpression is erased to the base JSXElement.
@aleclarson Yes, this would be the change which would hopefully allow that.
Yeah, we got a lot of the way where with the new `LibraryManagedAttributes` entrypoint we added for react last release; but that just fixes up the props, the return type...
I have https://github.com/weswigham/typescript-go/pull/1 separately open with the baseline changes, because if I merge those into this PR, this change goes from "practically unreviewable" to "actually impossible to navigate in the...
> I'm not sure how much you want eyes on the contents of the PR yet but I'm happy to look if you do At this point, eyes are welcome,...
The baselines at https://github.com/weswigham/typescript-go/pull/1 have something like 2026 deleted `.types.diff` and `.js.diff` files, so there's certainly some amount of progress here~