Interesting article. If i understand correctly, Kent would not split a simple component that just contains many many html elements.
I disagree and would split this component right away. The worst case scenario: I have a few extra components included in my main component that are easier to read and have meaningful names.
If I may ask, how large is your largest file on the project you are working on? I am onboarding in a new project where I saw components with over 1000 lines of code. Horror!
JavaScript wrangler.
Check out my books!
Web API Cookbook:
https://www.amazon.com/Web-API-Cookbook-JavaScript-Applications/dp/1098150694
Modern CSS:
https://www.amazon.com/dp/148426293X
Interesting article. If i understand correctly, Kent would not split a simple component that just contains many many html elements.
I disagree and would split this component right away. The worst case scenario: I have a few extra components included in my main component that are easier to read and have meaningful names.
If I may ask, how large is your largest file on the project you are working on? I am onboarding in a new project where I saw components with over 1000 lines of code. Horror!
A 1,000+ line component sounds like a nightmare, I think that is a perfectly valid reason to break it up :)
I guess you did not see 14000 lines of code :D believe me 1000 is not so bad at all