-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compose: Type withState
as any
#32326
Conversation
Size Change: +5 B (0%) Total Size: 1.04 MB
ℹ️ View Unchanged
|
That's a great idea. The |
79f798e
to
112ff78
Compare
withState
in a naïve waywithState
as any
de7c74d
to
63f706d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The project builds correctly, all tests pass, and there are no runtime changes.
LGTM 🚀
Description
I'm fairly certain these types are incorrect. We just need something that works even if we throw
@ts-ignore
all over the place or, worst case, type the return type asany
.I've proposed deprecating this function in the weekly core-js meeting.
Part of #18838
How has this been tested?
It's really not.
Types of changes
New feature.
Checklist:
*.native.js
files for terms that need renaming or removal).