The original post was published at iamtk.co
This is part of the Frontend Challenges Series.
Today I finished a frontend challenge and I had a bla...
For further actions, you may consider blocking this person and/or reporting abuse
Impressive end-to-end walkthrough. Thank you!
Thanks! glad you liked. Any feedback is always welcome!
Wow..I did something like this in my tech company and I know how technical it's to build something like this. You really did well bro. I loved the way you arrange your code and your documentation is top-notch. Kudos!!!
Thank you! I really appreciate that!
I can't read with this font
The body text font? Is it too large/wide?
oh nevermind
I hope you can read without any problem. Let me know if I can do anything to solve this issue!
Great job!
Thanks for sharing!
Does Context better in your case in terms of performance ?
Thank you! Really appreciate! :)
The Context API can be a performance bottleneck if used in the wrong way.
If you wrap your component and use a consumer only it really need to be used, you "solve" prop drilling and re-render only the necessary parts of the component (components that directly use the provider value).
You need to always be careful when implementing a context api driven component and keep track of the re-renders in your component. Other state management libraries could be a better choice for more complex cases.
Thanks for explanation. Appreciate it
Where did you get this challenge from? Did you make it by yourself?
It's very interesting article!!! Thanks for sharing it!!!
It was part of an interview I did in the past!
Thank you, really appreciate the comment!
dude it´s awesome that challenge and i like your approach, good job
Thank you, really appreciate the comment! I put a lot of work on the challenge and the post.