Please make more videos like these. Despite being a developer with 3 years of experience, I have literally learned at least 3 to 4 new things in just 26 minutes of absolutely smooth explanation.
Same here although I don't agree with few stuffs such as using recursion or the event bubbling thing (that will complicate things with typescript) but still great content.
@@adarshshete7987 don't do that please. React delegates all the events already. It was core JS code where event delegation was required to avoid attaching events on new child event addition.
To make the code more flexible and scalable, before flattening the 2d array, you can make a ref of the number of columns and rows. And then write inline styles to repeat the grid template accordingly. This way, even a rectangular shape can be rendered.
Also, I have an alternate approach, which would require lesser calculations while unloading. If we abstract the Box into a separate component and provide its own state of selected, and on selection, we pass the deselect function as a callback, and add that cb into an array. The moment unloading begins, you can just iterate through this array of callbacks and call the cb. It will deselect in the order of insertion. Rest everything remains the same.
Instead of using shift method which is O(n), we can just make use of closures and create a variable for index in unload, and use that to get value from keys array, then increment it afterwards
Thanks man, one thing that came to my mind is while unloading, instead of using unloading state to control the click event, we can get the parent div element and make its pointer-events to none
An optimization to add is to make unloading a ref. It isn't technically state, as it only serves to short-circuit the click handler. The benefit is that a ref won't cause a render cycle, where the useState would
I have one point to raise, at the time of selecting set over objects, you said it's not reliable, i agree with you on that but set is also not reliable because there is no guarantee of getting the data in the same order of insertion. May be we can use array with the checks of existing indexes
Hey man! Thanks for another great video. I had a few questions here: 1) Why flatten the array? The 2D array provided might have the row and column details but when you flatten, you might lose that and is being hard coded to 3 columns and n rows. 2) Using of non-primitive data structures in the dependency array, wouldn't it defeat the purpose of memorizing? Also, I left you a message on reddit yesterday, I just wanted to thank you for the platform and the videos!
I wanted to simplify the problem that is why flatten it. Ideally, it should be configurable and no hard coded CSS. Columns count should change as per the data. If you mean selected then we need an effect whenever it changes. It is a state and unless explicitly changed, we will get the same value across re-renders.
I feel like while the current approach works, it relies on a React "quirk" rather than a feature. Essentially, the point of creating the removeNextKey was to get around the problem of stale state which would otherwise cause the keys to be set to the old state again and again (thus never unloading). I think a better approach is to create a new state variable called unloading, and when the unload function is called for the first time, set the unloading state variable to true, this will cause all effects to be propagated through only the one useEffect which increases predictability and readability. The flow would be: The selected boxes exceeds the length of the boxes useEffect triggers unload unload -> setUnloading(true) unload -> update state of the set This update triggers the useEffect again Since unloading is true, the unload function is called again with the new updated state Terminating condition is simply the keys running out Keeping a single source of truth to state updates is pretty essential IMO
I came prepared for Java LLD round, however the interviewer was really cruel, and he started with dsa question, thinking it's a dsa round. Later for LLD, he said I have only 1 front end question, no java questions, and as this position was for full stack, I had no options but to go ahead. He asked this type of question, and surprisingly I was able to come up with working solution. However I couldn't answer some questions on react as I was prepared for java. For sure Im rejected this time. Interviewer made some comments like - - 'do u expect me to tell u the complete steps?' when I asked him that I may need some syntax help, as Im not prepared for react. - 'are you just assuming the solution to be this, and try more probable reasons ?' when I was trying to find a reason for useState event. literally such negative comments, downshifted my morale
Was it stated somewhere that the data always will be 3x3? The CSS is hard coded to 3 columns, so if you get a 4x4 grid, it'll look weird. But otherwise great stuff. I learned a lot!
You can do both ways. Unless you have thousands/lakhs of boxes in the shape, the flat is quite fast. We can optimise if we feel there is a bottleneck after measuring.
@@DevtoolsTech i was not talking about optimization, maybe that 2d array can be there for a reason, and any new requirement comes and now we lost the track of the nested arrays, in that case we need to change logic right?
You can't predict what all requirements can come. Solve for the current problem unless current changes create a major tech debt. There could be n of future changes, what all can you accommodate without knowing the changes? It can lead to logic change or it might not.
Thanks Yomesh, I would like to mention that 5th point in functional requirement of this question is a bit confusing "During de-selection, user should be able to select a new box as in disable any box interaction." Can you please fix it.
I did not get the purpose to make it flatters i mean that data could be indicate allocation of row and column some how also can’t we just simply count what the length of array and how many box are selected once both match it should refresh all box…
There could be multiple ways to solve it. Making it flat just simplifies the logic. We can do with flat too and change the logic. Feel free to implement it and share it with all. Thanks! 🙌🏼
what if instead of using opacity zero, I choose not to even render the box if the array element is 0, do we still need that if condition 12:39 ? Btw I solved it but looking at your code there's a lot of improvement needed for optimisation 😝
I chose to render to keep the UI consistent and not run into issues where CSS behaves weirdly due to missing elements. If it works well for you then you can skip conditions. I am glad you learnt something new! 🙌🏼
Imagine being asked this question in 45 minutes 😂. I mean people shouldn’t judge a candidate based on a single question . Many would freak out and won’t be able to build it in that period of time.
@@DevtoolsTech ChatGPT - In React, event delegation is automatically handled to some extent through a mechanism called Synthetic Events. React doesn't attach event listeners directly to child DOM nodes. Instead, it attaches them to the root node (usually at the document level or the component's root). This is part of React's event handling optimization. Gemini - While React doesn't explicitly mention "event delegation" in its documentation, it does implement it under the hood. Here's what you need to know: How React handles event delegation: Root Container: In React 17 and later, event listeners are attached to the root DOM container where your React app is rendered. This means that a single event listener at the root handles events for all your React components. Event Bubbling: React leverages event bubbling, where events triggered on a child element propagate up the DOM tree until they reach the root. This allows React to capture events on any component within your application. Synthetic Events: React uses synthetic events, which are cross-browser wrappers around native DOM events. This ensures consistent event behavior across different browsers.
This doesn't solve the question mentioned in the video. There is no event handler. You are setting the indexes to true in a sequence and then deselecting them. It is a partial solution.
Question link: devtools.tech/questions/s/how-to-create-an-interactive-shape-based-ui-uber-frontend-interview-question-or-javascript-or-react-js---qid---6FVH1ZMWMXd4uZ8WAGEi
Best coding practices: ruclips.net/video/9g1rYWJvvzY/видео.htmlsi=3KR-lnNf7GCcE_RU
Other top questions --
LinkedIn: ruclips.net/video/6euTBVDCD6o/видео.html
Facebook: ruclips.net/video/7DJCpgc6V94/видео.html
Atlassian: ruclips.net/video/3OxMsnP78zg/видео.html
Klarna: ruclips.net/video/Py_bXjSMyTc/видео.html
MakeMyTrip: ruclips.net/video/yHg0bvNqJEQ/видео.html
Microsoft: ruclips.net/video/Iv1gZN900uc/видео.html
AWS: ruclips.net/video/PFo1ZQBv4hA/видео.html
Custom Loader: ruclips.net/video/E01XdDQgzDM/видео.html
Practice with us: topmate.io/yomeshgupta
Please make more videos like these. Despite being a developer with 3 years of experience, I have literally learned at least 3 to 4 new things in just 26 minutes of absolutely smooth explanation.
Glad to hear that! More videos coming soon! 🚀
Same here although I don't agree with few stuffs such as using recursion or the event bubbling thing (that will complicate things with typescript) but still great content.
I did not think of using event delegation and attributes to record which box is clicked 😅😅😅. Awesome video
Glad to see you learnt something new today! 🙌🏼
Yes, using event handler on parent, I have not used this pattern before, glad to learn this, thank you.
@@adarshshete7987 don't do that please. React delegates all the events already. It was core JS code where event delegation was required to avoid attaching events on new child event addition.
@AbhishekJain1992 Please share documentation around it.
To make the code more flexible and scalable, before flattening the 2d array, you can make a ref of the number of columns and rows. And then write inline styles to repeat the grid template accordingly. This way, even a rectangular shape can be rendered.
Also, I have an alternate approach, which would require lesser calculations while unloading.
If we abstract the Box into a separate component and provide its own state of selected, and on selection, we pass the deselect function as a callback, and add that cb into an array. The moment unloading begins, you can just iterate through this array of callbacks and call the cb. It will deselect in the order of insertion.
Rest everything remains the same.
Thanks for sharing your approach! 🙌🏼
First time i watched, i realized many things i dont know 😅😂 but i enjoyed and i will watch again and again, not only for logic also for improving eng😂
Glad to see you learnt something new! More coming soon. 🙌🏼
Learned alot! tried to solve it myself but couldn't at 1st go. thanks to you learned so many important and new stuff.
Glad to hear that! New video coming out this Sunday. Watch out for that! 🙌🏼
Instead of using shift method which is O(n), we can just make use of closures and create a variable for index in unload, and use that to get value from keys array, then increment it afterwards
Could you please share the code? Thanks!
@@DevtoolsTech I JUST STARTED LEARNING HTML CSS JS, AND IM SHOCKED TO SEE ALL THESE THINGS IN FRONTEND
@@kYt0-cz3hk There is a lot more. You will learn with time and efforts. Just keep at it!
@@DevtoolsTech but i didt knew all this existed sadly, any way i can atleat know what all things exist
May be try roadmap.sh for a structured learning.
This video I watched randomly, but worth for wach learn many things. Thank you
Glad to hear that! Many more coming soon! 🙌🏼
same bro
Thanks man, one thing that came to my mind is while unloading, instead of using unloading state to control the click event, we can get the parent div element and make its pointer-events to none
Thanks for the suggestion! I did that to be double sure incase some css overrides happen!
Thank you! I am learning the way how you are explaining tradeoffs why to DS to choose , explaining technicalities
Glad to hear that! 🙏🏻
Amazing sir ji 🎉 I am a react developer and I see the first time optimization video.... Great 👍👍👍 keep it up ❤❤❤
Thank you! More to come. 🙌🏼
An optimization to add is to make unloading a ref. It isn't technically state, as it only serves to short-circuit the click handler. The benefit is that a ref won't cause a render cycle, where the useState would
I JUST STARTED LEARNING HTML CSS JS, AND IM SHOCKED TO SEE ALL THESE THINGS IN FRONTEND
in my opinion, using setInterval instead of setTimeout may be better option, and clear the interval when all the card deselection completed.
Both works in this case. Thanks for the suggestion!
I have one point to raise, at the time of selecting set over objects, you said it's not reliable, i agree with you on that but set is also not reliable because there is no guarantee of getting the data in the same order of insertion. May be we can use array with the checks of existing indexes
In Set, order of insertion is preserved. I used it because order of insertion is preserved and look up is O(1)
Hey man! Thanks for another great video. I had a few questions here: 1) Why flatten the array? The 2D array provided might have the row and column details but when you flatten, you might lose that and is being hard coded to 3 columns and n rows. 2) Using of non-primitive data structures in the dependency array, wouldn't it defeat the purpose of memorizing?
Also, I left you a message on reddit yesterday, I just wanted to thank you for the platform and the videos!
I wanted to simplify the problem that is why flatten it. Ideally, it should be configurable and no hard coded CSS. Columns count should change as per the data.
If you mean selected then we need an effect whenever it changes. It is a state and unless explicitly changed, we will get the same value across re-renders.
I feel like while the current approach works, it relies on a React "quirk" rather than a feature. Essentially, the point of creating the removeNextKey was to get around the problem of stale state which would otherwise cause the keys to be set to the old state again and again (thus never unloading). I think a better approach is to create a new state variable called unloading, and when the unload function is called for the first time, set the unloading state variable to true, this will cause all effects to be propagated through only the one useEffect which increases predictability and readability.
The flow would be:
The selected boxes exceeds the length of the boxes
useEffect triggers unload
unload -> setUnloading(true)
unload -> update state of the set
This update triggers the useEffect again
Since unloading is true, the unload function is called again with the new updated state
Terminating condition is simply the keys running out
Keeping a single source of truth to state updates is pretty essential IMO
I don't think it is a quirk. Both approaches work fine. Thanks for sharing! 🙌🏼
I came prepared for Java LLD round, however the interviewer was really cruel, and he started with dsa question, thinking it's a dsa round.
Later for LLD, he said I have only 1 front end question, no java questions, and as this position was for full stack, I had no options but to go ahead.
He asked this type of question, and surprisingly I was able to come up with working solution. However I couldn't answer some questions on react as I was prepared for java.
For sure Im rejected this time.
Interviewer made some comments like -
- 'do u expect me to tell u the complete steps?' when I asked him that I may need some syntax help, as Im not prepared for react.
- 'are you just assuming the solution to be this, and try more probable reasons ?' when I was trying to find a reason for useState event.
literally such negative comments, downshifted my morale
Sad to hear. Hard luck! Don't lose faith, sometimes interviews go bad due to factors not in our control. We can hi just learn and move on.
Nice video bhai
Was it stated somewhere that the data always will be 3x3? The CSS is hard coded to 3 columns, so if you get a 4x4 grid, it'll look weird. But otherwise great stuff. I learned a lot!
In the question, it was mentioned it is 3x3 for now. However, I agree we can go for a configurable approach where grid of any size should work.
Thanks for this types of videos and questions. also you well explained ✌✌
More coming soon! 🙌🏼
Bro create much more videos related thanks ❤
In your opinion, what is the difficulty level of this problem?
Great Video.
It would be a beginner/intermediate problem depending upon the kind of conversation that follows the solution.
Is Flattening the array is good idea?, what about scalability?
I think it will afftect scalability, how will you tackle that?
You can do both ways. Unless you have thousands/lakhs of boxes in the shape, the flat is quite fast. We can optimise if we feel there is a bottleneck after measuring.
@@DevtoolsTech i was not talking about optimization, maybe that 2d array can be there for a reason, and any new requirement comes and now we lost the track of the nested arrays, in that case we need to change logic right?
You can't predict what all requirements can come. Solve for the current problem unless current changes create a major tech debt. There could be n of future changes, what all can you accommodate without knowing the changes? It can lead to logic change or it might not.
Two query : const removeFill = ()=>{
if(allSelectedKeys.length){
const currentKeys = allSelectedKeys.shift();
setClickedCells(prev=> {
const updatedKey = new Set(prev);
updatedKey.delete(currentKeys);
return updatedKey;
})
setTimeout(removeFill,500)
}
}
setTimeout(removeFill,100) why we are doing const updatedKey = new Set(prev);
We are creating a copy and removing keys from it. We don't want to mutate original value.
Very interesting problem and you explained it really well, thanks ❤
Thank you! Many more to come. 🙌🏼
No need for new state for loading, set size is good enough.
Thanks Yomesh, I would like to mention that 5th point in functional requirement of this question is a bit confusing "During de-selection, user should be able to select a new box as in disable any box interaction." Can you please fix it.
Hi, thanks for pointing it out. I will fix it! 🙌🏼
So this is how elite devs code like
Hahaha 😅
Really Nice. Would like to learn more. Subscribed and bell icon clicked.
Thank you! 🙌🏼
What is the salary range for frontend developer at uber
Depends upon many factors like experience, skills, profile, and more but it is good
@@DevtoolsTech how much one can expect with 1-2 years of experience?
I did not get the purpose to make it flatters i mean that data could be indicate allocation of row and column some how also can’t we just simply count what the length of array and how many box are selected once both match it should refresh all box…
There could be multiple ways to solve it. Making it flat just simplifies the logic. We can do with flat too and change the logic. Feel free to implement it and share it with all. Thanks! 🙌🏼
I learned something new, today.
Glad to hear that! 🙌🏼
what if instead of using opacity zero, I choose not to even render the box if the array element is 0, do we still need that if condition 12:39 ?
Btw I solved it but looking at your code there's a lot of improvement needed for optimisation 😝
I chose to render to keep the UI consistent and not run into issues where CSS behaves weirdly due to missing elements. If it works well for you then you can skip conditions.
I am glad you learnt something new! 🙌🏼
Imagine being asked this question in 45 minutes 😂. I mean people shouldn’t judge a candidate based on a single question . Many would freak out and won’t be able to build it in that period of time.
This is commonly asked in Uber's Frontend roles!
@@DevtoolsTech 😂 I’m doomed bro. I can build but in interview it’s whole different game
You need to practice! That is the only way. I don't want self plug but you can try mock interviews. Try something like
topmate.io/yomeshgupta
Roadside coder also solve this type of question few months back
Haven't seen his video yet. More the no. of resources better for us all! 🙌🏼
? was it to be solved using a ui framework or plain JS dom mainpulation will work?
Question was asked using React.js but could be solved with Vanilla JS.
Was really helpful and think I learnt something new, thank you !
Glad to hear that! 🙌🏼
experience level for this interview round ?
SDE 1/SDE 2
Awesome 🎉
Thanks Bhaiya...❤😊
You are welcome! ♥️
Source code?
Will share soon.
Please don't teach wrong things. React does the delegation itself.
Please share a valid resource or documentation to backup your claim.
@@DevtoolsTech you can read about it in official document on react synthetic events.a
@@DevtoolsTech ChatGPT - In React, event delegation is automatically handled to some extent through a mechanism called Synthetic Events. React doesn't attach event listeners directly to child DOM nodes. Instead, it attaches them to the root node (usually at the document level or the component's root). This is part of React's event handling optimization.
Gemini - While React doesn't explicitly mention "event delegation" in its documentation, it does implement it under the hood. Here's what you need to know:
How React handles event delegation:
Root Container:
In React 17 and later, event listeners are attached to the root DOM container where your React app is rendered. This means that a single event listener at the root handles events for all your React components.
Event Bubbling:
React leverages event bubbling, where events triggered on a child element propagate up the DOM tree until they reach the root. This allows React to capture events on any component within your application.
Synthetic Events:
React uses synthetic events, which are cross-browser wrappers around native DOM events. This ensures consistent event behavior across different browsers.
Thanks for sharing. I will read about it.
Could you please your LinkedIn so that others folks can connect and learn from your knowledge too. Thanks!
let arr = []
let getState = []
const statesArr = (n)=>{
return Array(n).fill(0)
}
const handleClick = (index)=>{
arr.push(index)
getState[index] = 1
if(arr.length === getState.length){
setTimeout(() => {
deSelect()
}, 2000);
}
console.log('select:',getState)
}
const deSelect = () =>{
i = 0;
while(i {
handleClick(element)
});
}
main()
This doesn't solve the question mentioned in the video. There is no event handler. You are setting the indexes to true in a sequence and then deselecting them. It is a partial solution.
@@DevtoolsTech ok sir