Thanks this helped a lot, but think you should have use Edge (top / bottom) so you can rearange the list

Hi! your explanation is too good. can you make a video for react virtualized(grid) with PND . it would be great then

Dude... The music is to much.

Thank you for this tutorial, would love to see a repo to play with

Is there a repo for this example ?

Thanks mate. So does that means Suspense should always pair up with Error Boundaries as Suspense will not handle errors.

Thank you for this awesome videos 👏👏,

This is great! Do you think there would be an easy way to use this library to make a nested drag and drop container? For example so you could have nested to-do's within a todo? I've tried personally but im struggling to get a placeholder for it.

Watching this after one whole year😂this is still relevant and helpful 👍 nice diagram

Hi juntao, you videos are amazing, I am not sure if I can watch it with filtering with your image, looks like your image is cutting some contents for me, Thank you

Thank you :D

Thanks man

Thanks for your prqctical contents, please create some contents about handling global state management through services

❤nice

thank you so much !

Thanks for sharing this principle, my man. Keep it up!😊

Using JS for such a task is not a good idea. I mean, TS will be a better option, since the data structures are well known, and making mistakes is very easy without a type system

Thanks!

Nice video, I always wanted to try the codemod, this video spark my curiosity and I think I'll use it for my migration, thanks for sharing 🙌

Your channel is criminally under-subscribed. This is fantastic content.

excellent

Amazing explanation bro!

Great one, I have been enjoying these your design pattern videos and it's been good. Please can you be increasing your zoom level maybe 2 or 3 more times of your code editor when recording, it's pretty hard to read your code even on 1080p as the size is small. Thank you, keep up the great work

Thanks for the simple explanation. Good job! Keep on it!

Please, provide the github code

Amazing working mate, thank you so much for sharing

Translation? OMG! This is so gorgeous

I am a humble junior dev and I thank you so much for the very helpful work.

Thank you for the video. One comment, I would disable Webstorm types hints to be more ide agnostic

does not matter in most of cases, but i would place all filtering pipes as close to start of the pipeline as possible to first eliminate items and then mapping them. sometimes it helps not only performance-wise, but more of even in obtaining narrower types down the line. thank you for video

Thanks for sharing

the mind map is top-notch, I think thats how one must go about every problem statement on systems design. Thanks !

Thanks for sharing this, really appreciated! One tip if I may, while refactoring, instead of moving the original component, it would be cleaner (and smoother) to extract its content into another component and move that one into another file. That is to say leave "MenuList" where it is, extract the content into a "MenuListOld" component that you will move into another file, then return it from the "MenuList" straightaway. This will basically leave the same behaviour as before and create the space for the branching logic without having to change the consumer side. Hope that makes sense :)

thanks for the content

Excellent! What extension are you using to show function usage?

Thank you

promo sm 💖

这里感觉不需要useEffect(主要用在有副作用或者某些生命周期) ？ total是基于checked和传进来的amount计算的，total不是应该完全可以当一个const total = 。。。。。来计算吗？ tip也是. 每一次checked或者props的改变,这个组件都会rerender, 那么tip, total都会重新计算. 不知道我的理解对不对啦.感觉有点绕. ``` function Detail({ amount }) { const [checked, setCheck] = useState(true); const tip = parseFloat(Math.floor(amount + 1) - amount).toPrecision(2); // 直接计算 const total = checked ? Math.floor(amount + 1) : amount; // 直接计算 const handleOnChange = (e) => setCheck(e.target.checked); return (); } ```

Thanks man, extremely useful!

Please keep continuing teaching like this...I've seen so many system design videos but none of them had the clarity of the mind- map you gave. Kudos!!!

Am I the only one asking himself how is this frontend? I there are 5 topics on which I do not need to be an expert on, but there are expecting me to actually know what I am talking about HOW is this not fullstack or backend?

Can we mock POST api too with this tool

The video is great but the background music can be distracting

Those naming conventions are must (ex: build, predeploy, deploy) or we can give any name ??

This is what I was looking for, a simple but visual explanation. Thank you

that was not I was expect.

so cool, a fellow from Kunming

Not much people what is magic behind NPM BUILD. THanks for the video~

ty very much!