-
Notifications
You must be signed in to change notification settings - Fork 839
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
Drag and drop - use new fork #6187
Comments
@thompsongl sounds good. We've received some very positive feedback about migrating to the new fork so I don't anticipate it will be a significant engineering challenge. Naturally there's more than engineering to consider. Let me know if there's anything myself or other maintainers can help with 👍 |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
❌ We're automatically closing this issue due to lack of activity. Please comment if you feel this was done in error. |
Re-opening as still valid / related to React 18 |
This upgrade has happened as part of our React 18 feature branch (which is still not yet available in main / as a release, but will be once the feature branch is deemed ready to go - hopefully in the next month or so here). See #6868 Thanks so much again @Xhale1 for your amazing work with the fork! The upgrade was flawless and cleaned up a bunch of our tests. ❤️ Y'all are amazing! |
Hello!
react-beautiful-dnd
is no longer being maintained by Atlassian per their readme. It currently doesn't support React 18 and strict mode.Another developer and myself created a fork @hello-pangea/dnd which improves a few things:
@hello-pangea/dnd
is a drop-in replacement forreact-beautiful-dnd
and should require no changes to support aside from renamed imports.Would Elastic be open to a PR migrating to
@hello-pangea/dnd
?The text was updated successfully, but these errors were encountered: