4 ms·
> const headerClasses = [(list of Tailwind classes here)]; > <header className={...headerClasses}>...</header> Why wouldn't they extract the header as a high
by balfirevic 4y ago
> const headerClasses = [(list of Tailwind classes here)];
> <header className={...headerClasses}>...</header>
Why wouldn't they extract the header as a higher-order component? That would make more sense even without Tailwind, and I haven't heard anyone in the Tailwind community advocate against that.
- have_faith 4y agoI think this is just an example but `header` is a standard HTML element. It's not always necassary to seperate every single element into it's own component. Every time you make a framework component you add overhead to the rendering of the app.
- replygirl 4y ago> Every time you make a framework component you add overhead to the rendering of the app. not true, separating components by concern can save you a lot of fiddling with memoization
- balfirevic 4y ago> It's not always necassary to seperate every single element into it's own component. It's not necessary but in the given case it's obviously useful as there is more to abstract than just the html element - the styling.