-
Notifications
You must be signed in to change notification settings - Fork 983
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
Support React v. 18 #844
base: master
Are you sure you want to change the base?
Support React v. 18 #844
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit f28d4ac:
|
@clauderic please review |
…onentType` * `React.SFC` type is no longer supported with React v. 18 (becomes `React.FC`) * Since `React.ComponentClass` was specified the proper type now is `React.ComponentType` that covers both `React.FC` and `React.ComponentClass`
yes please review |
@chrishawn I'm afraid it might never be introduced. The lib is considered deprecated and further enhancements won't be merged. Only security fixes. See @dnd/kit as an alternative. Anyways migration to @dnd/kit is not obvious and it'd be perfect to have the support of React v18 here. The newest version of React does ensure backward compatibility. I see that |
Would also like to see this merged. We can also not migrate away currently to another package. So would really like to see 18 official supported here. |
@clauderic : Please support that. We are using this package on so many pages so it will be a huge effort to migrate. Since the methods are still there (only deprecated), I really hope that this will be merged. Thanks!!! |
Hello, |
@clauderic Is there any migration guide to dnd-kit? |
Hello, Any updates for when it will be released? Thanks everyone for the work. |
Hi guys, merge it please. |
Fixes #838