Update react-beautiful-dnd to the latest version 🚀 #158
Conversation
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 9.0.2 just got published.Update to this version instead 🚀 Release Notes9.0.2Engineering healthCommitsThe new version differs by 7 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for 10.0.0Fixes |
Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Update to this version instead 🚀 Release Notes for 10.1.0
Highlights 🤾♀️
Beautiful 🏔This release pushes We have removed instant movement (snapping) when moving between lists. Snapping breaks the visual language of moving physical objects around that ✅ No snapping when moving between lists
❌ This is what it used to be (snapping in the 🏠 home list after a drop)
Blog: Beautiful interactions 📝There was a huge amount of work to remove snapping when moving between lists. Who would have thought? Not me 🥵. I wrote a blog which goes over the journey of this feature in depth. Personally, I think it well worth your time! 📝Blog → Beautiful interactions: Crafting elegant and robust drag and drop animations New logo 👩🎨
We have moved to a logo that encapsulates the playfulness and delight that we are striving for with Blog: Logo creation 📝Maryanne Nguyen, a very talented designer at Atlassian, has detailed her creative process in creating the new 📝Blog → maryannemade: More predictable touch dragging 📱
Unfortunately, heavy presses can cancel a drag. It can be tricky at times to get the right amount of pressure to correctly use touch dragging. This can be frustrating for users. We have added an option for you to opt-out of respecting force touch interactions. This option will disable force press interactions on the drag handle. However, it allows for a more consistent touch dragging interaction. We have added <Draggable draggableId="draggable" + shouldRespectForceTouch={false} >
Should force touch be respected by default?Right now I have created a request for discussion to collect other people's thoughts on what the default should be. Simplified home list styling 🏠We have added a new value to the type DroppableStateSnapshot = {|
isDraggingOver: boolean,
draggingOverWith: ?DraggableId,
+ draggingFromThisWith: ?DraggableId,
|};
In this example we set the
Overhauled documentation 📖We have totally overhauled our documentation to be easier to find and use information. Our The For new comers and evaluators 👶Information in the
For consumers 👩🎤
Documentation engineering health 👨⚕️
Refreshed examples 🦸♂️ #1096We have made our examples brighter and more colourful
We have also upgraded to Storybook
Other improvements
Fixes 🐛
Engineering health
|
Update to this version instead 🚀 Release Notes for 10.1.1Fixes 👩⚕️
Documentation
Engineering health 👷♀️
(Minor) breaking changes are coming soon 💥We will soon be publishing
More details: #1194 CommitsThe new version differs by 13 commits.
See the full diff |
|
|
|
|
|
|
|
|
|
|
|
Version 9.0.1 of react-beautiful-dnd was just published.
The version 9.0.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of react-beautiful-dnd.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
9.0.1Fixes
DragDropContext#720. Thanks @faiwer for finding this one, and for the great issue detail!Soon ⏳
We have been working hard over the last few months on some super exciting improvements and new features. These should be landing in the next month or so!
Commits
The new version differs by 170 commits.
568cdbev9.0.1e7197adUpdate stylelint to the latest version 🚀 (#718)619b0ccUpdate eslint-config-prettier to the latest version 🚀 (#705)48e0d84Fixing memory leak in DragDropContext. Fixes #715 (#720)b939e9aUpdate Hook types to returnmixedvsvoid(addresses #695) (#704)ac63abeUpdate tiny-invariant to the latest version 🚀 (#702)0215cb2Giving love to debug (#701)2d6504fv9.0.031e7b3cFixing disabled on launch. Closes #693 (#696)55aa7c3Update testcafe to the latest version 🚀 (#698)5de1a93Update flow-bin to the latest version 🚀 (#686)20adb8aFixes broken test filename (#697)19b7ebfUpgrade to babel beta 56 (#687)3006259ci: run greenkeeper lockfile management steps before checking if the lockfile is OK (#684)1a81e90bumping react and loosing restriction on prop-types (#681)There are 170 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴