Find me on medium
Writing clean code is something that becomes mandatory at some point in your career especially while you're trying to obtain you...
For further actions, you may consider blocking this person and/or reporting abuse
Good tips, thanks. In regards to "folderizing your components" - do you ever run into issues with so many files called "index.js"? That's just a little thing - but it always kind of confuses/bugs me when I have a bunch of index.js functions open, and I have to figure out which is which... Any tips for that?
No problem! And what I do is to not write anything in the index.js but to
export defaultthe actual file in the same directory.src/components/Tooltip/index.js:
You can also put a package.json in place of
index.jsas below:src/components/Tooltip/package.json
Either way the end goal is to write code in the actual
Tooltip.jsfile.Ahhhh - got it. Thanks! that's a good idea.
No problem :)
Thank you for the great post as usual.
I agree with
10. Use useReducer if useState becomes complexnot just because you can co-locate concerns but also because you can extract that functionality out as you mentioned in6. Put Independent Functions Outside of Your Custom Hooks.I had to create a context (using tips on How to use React Context effectively) and had very easy time make it into a context value.
Sorry don't read the whole article after this🤢😱
You just showed an amazing list of good practices. Thanks for sharing them here
Your very welcome. Glad to hear that, Usman Khalil!
It's crucial to prioritize writing clean code, especially when aiming to land your first developer job. Clean code demonstrates your ability to be a team player fnaf world and can significantly impact your success in a job interview.
Great post! Thank u!
I think you might be interested in sort-imports plugin for eslint, it's configurable and could potentially do the import sorting for you.
Nice article 🙂