1. "This has a bug let me show you" 2. "The bug actually is not here" 3. "This is still clearly the fault of the author, since the example is misleading" 4. "But here is a bug" 5. "Interesting" Listen, it is pretty clear the author of the example is no react dev, still the attitude is really a problem. "Damn I was wrong, learned something new" is a lot nicer than the other person always being at fault
This video is great for 2 reasons: it shows a neat pain-killer for drag-and-drop, and it showcases that no matter the additional tech, it's a major pain in the lower back to figure out what the React code will effectively do at runtime 🤓
It's normal that it doesn't rerender and it doesn't break, because even if you move a dom element, as long as the istance is the same it will work. This is the same way portals work. What you don't have to do is cloneElement and delete the original one, in that case react will break. Using key "breaks" it because react will take each element and destroy them, and create a new instance in the DOM. What should be clear to people is that what you have into JSX doesn't necessarily match with the actual DOM, JSX it's only a set of instructions that tell react what elements you have and what's their initial position, but you can move whatever you want with a js script. Potentially you can even remove an element from the root document but keep it in memory, react will still track it.
It's great that this works for vanilla js. Though for react, the formkit drag and drop seems much better. Barely any setup, just give it a list and plug in the ref for basic functionality. dndkit is fine as well, but it's definitely a lot more manual if you want to keep state synced from what i remember from using it. Anything is better than beautiful dnd though.
Drag and drop is one of those things that seems like it should be relatively simple, then you try to do basically anything with it and realize how unbelievably complex it gets so quickly
Honestly I doubt anyone would run into those edge cases you speak of. More than edge cases, this was default react behavior. It's the same with portals. If you re-render the parent of the portals, of course the portals will re-render. What you want is external state to be unrelated to swapy so the container itself never re-renders with a different key, and then it's just fine to have state anywhere else. The only time swapy broke was when you changed the key, so react thought the container was an entirely new div.
Uncommonly great video quality. I feel like this will get less views than other stuff, but more people will come back to this video and use the information. A+++ SUPER FAST SHIPPING && SUPER CLEAN
I love auto animate, I’ve used it in pretty much all of the react apps I’ve worked on, it just gives the right amount of animation needed, not too fancy, just the needed! ❤
Although react-beautiful-dnd is no longer actively maintained other than bug fixes, it is still the most complete solution to this day. Even Linear uses it-it's still not _perfect_, but having tried a ton of other solutions, I can hardly recommend anything else really. Not even DndKit.
To be honest, I've felt like DndKIt hasn't really been ready for production since it's early "beta" release, compared to react-beautiful-dnd. It seems to lack a ton of features and edge-cases.
Good to know I wasn't the only one that felt that way. It felt like I was running into edge case after edge case, which could have been solved with two lines of documentation.
I'm curious to hear your thoughts on the Pragmatic drag and drop from Atlassian. I'm just investigating it now, and while it takes a bit more to set up, I like how it's applicable to a lot of different DnD situations.
"Can't handle react renders' edge cases well" So it will work fine with all other frameworks So the problem is not the library, it's React's re-rendering model
0:15 I had to manually implement drag and drop for a custom widget using pyqt5 for a coursework project once. it took 10 hours to write the 50 lines of code needed to make it work.
The reason the App doesn’t rerender is because there is no state update. There are dom events happening that switch the placements of the boxes but react isn’t aware of the changes because there is no set state function being called
I thought it was going to be a demo of the LIBRARY, instead we got a dude trying to break react, which btw, is so unnecessary for this example anyways...
This morning I found out about something I have never noticed on Firefox before. I had a a hidden checkbox input with default value to checkbox. When you change the value and refresh the page, Firefox update everything on the page but does not change the last value of that input. I cant find any cache/local storage ref to the value. It just does it somehow. It doesn't on chrome. I am not using any lib or framework by the way or cache mechanisms.
Why doesn’t React address the issue of using a vanilla JS library? Every other framework under the sun makes it trivial to wrap any vanilla JS library.
bruh drag and drop is legit the worst problem I spent months trying to implement it in my custom UI framework I made for fun, it required a rewrite of half the framework and the code was still supremely cursed
out of curiosity, when you found the problem/edge case with having a global state which updated causing any changes made to be reset - would having it stored in localStorage (as the example had) have prevented this? my thoughts being that the re-render would then fetch where things should be from localStorage or wherever and then rendered using that. (im still a somewhat react noob)
i don't get how react up to this day is so fragile. I don't see the benefit of it over the vue ecosystem where everything just works. including islands
Nothing in this video provide React to be "fragile". The simple explanation here is that if you update the DOM outside of React, React won't keep track of those changes. Updating the `key` will blow away the element and its children and result in a new node during reconciliation. Vue does not solve this, since it also relies on a VDOM. So both would "break" the same way. Only frameworks that uses the DOM as source of truth could potentially work (although there's likely other reasons it wouldn't).
Damn, all that shows me how backwards React actually is compared to the automatic reactivity system in Vue 3, you never run into mess like this, rather than spending time fixing re-renders you focus on business logic instead, amazed at how good Vue is compared to this, everyone should try it.
@MrSprinkles1F369 Ah ok cool they seem to be a bit different. my use case though react aria did a good job and was very simple to use . being buolt for react is a positive when its a react app.
Haven't played with the library but just watching it looks like changes to the JSX / VDOM break it? Maybe that's why they are using the localStorage on re-render as a workaround? You commented out that part so I wonder if it works again if you put the localStorage caching back in.
