Styled components: nested className selectors vs multiple styled components
0
In general, are there any significant performance differences between using one of these approaches over the other?
When using styled components I've noticed two common approaches:
- Have a styled parent component that uses className selectors to target child nodes for styling, and encapsulates those styles in the one place.
- Have multiple styled components for each individual node that requires styling, independent of any parent styled components.
1 - nested selectors
const MyComponent = styled.div`
display: inline-block;
position: relative;
.MyChildComponent {
position: absolute;
background: red;
}
.MySubComponent {
background: yellow;
}
`
// In use
<MyComponent>
<span className="MyChildComponent>A goose!</span>
<button className="MySubComponent">Click bait</button>
</MyComponent>
2 - discrete components
const MyComponent = styled.div`
display: inline-block;
position: relative;
`
const MyChildComponent = styled.span`
position: absolute;
background: red;
`
const MySubComponent = styled.button`
background: yellow;
`
// In use
<MyComponent>
<MyChildComponent>A Goose!<MyChildComponent>
<MySubComponent>Click bait</MySubComponent>
<MyComponent>
Obviously there are situational reasons to mix and match these approaches, and I'm not taking into consideration use cases where a component may be re-used throughout a code base. I'm instead asking in the context of large chunks of markup that are unlikely to change or be shared.
reactjs styled-components
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
add a comment |
0
In general, are there any significant performance differences between using one of these approaches over the other?
When using styled components I've noticed two common approaches:
- Have a styled parent component that uses className selectors to target child nodes for styling, and encapsulates those styles in the one place.
- Have multiple styled components for each individual node that requires styling, independent of any parent styled components.
1 - nested selectors
const MyComponent = styled.div`
display: inline-block;
position: relative;
.MyChildComponent {
position: absolute;
background: red;
}
.MySubComponent {
background: yellow;
}
`
// In use
<MyComponent>
<span className="MyChildComponent>A goose!</span>
<button className="MySubComponent">Click bait</button>
</MyComponent>
2 - discrete components
const MyComponent = styled.div`
display: inline-block;
position: relative;
`
const MyChildComponent = styled.span`
position: absolute;
background: red;
`
const MySubComponent = styled.button`
background: yellow;
`
// In use
<MyComponent>
<MyChildComponent>A Goose!<MyChildComponent>
<MySubComponent>Click bait</MySubComponent>
<MyComponent>
Obviously there are situational reasons to mix and match these approaches, and I'm not taking into consideration use cases where a component may be re-used throughout a code base. I'm instead asking in the context of large chunks of markup that are unlikely to change or be shared.
reactjs styled-components
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
In my experience, inverting the mapping ofstyles -> elementstoelements (components) -> stylesis invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors
– sliptype
Nov 20 '18 at 22:23
add a comment |
0
0
0
In general, are there any significant performance differences between using one of these approaches over the other?
When using styled components I've noticed two common approaches:
- Have a styled parent component that uses className selectors to target child nodes for styling, and encapsulates those styles in the one place.
- Have multiple styled components for each individual node that requires styling, independent of any parent styled components.
1 - nested selectors
const MyComponent = styled.div`
display: inline-block;
position: relative;
.MyChildComponent {
position: absolute;
background: red;
}
.MySubComponent {
background: yellow;
}
`
// In use
<MyComponent>
<span className="MyChildComponent>A goose!</span>
<button className="MySubComponent">Click bait</button>
</MyComponent>
2 - discrete components
const MyComponent = styled.div`
display: inline-block;
position: relative;
`
const MyChildComponent = styled.span`
position: absolute;
background: red;
`
const MySubComponent = styled.button`
background: yellow;
`
// In use
<MyComponent>
<MyChildComponent>A Goose!<MyChildComponent>
<MySubComponent>Click bait</MySubComponent>
<MyComponent>
Obviously there are situational reasons to mix and match these approaches, and I'm not taking into consideration use cases where a component may be re-used throughout a code base. I'm instead asking in the context of large chunks of markup that are unlikely to change or be shared.
reactjs styled-components
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
In general, are there any significant performance differences between using one of these approaches over the other?
When using styled components I've noticed two common approaches:
- Have a styled parent component that uses className selectors to target child nodes for styling, and encapsulates those styles in the one place.
- Have multiple styled components for each individual node that requires styling, independent of any parent styled components.
1 - nested selectors
const MyComponent = styled.div`
display: inline-block;
position: relative;
.MyChildComponent {
position: absolute;
background: red;
}
.MySubComponent {
background: yellow;
}
`
// In use
<MyComponent>
<span className="MyChildComponent>A goose!</span>
<button className="MySubComponent">Click bait</button>
</MyComponent>
2 - discrete components
const MyComponent = styled.div`
display: inline-block;
position: relative;
`
const MyChildComponent = styled.span`
position: absolute;
background: red;
`
const MySubComponent = styled.button`
background: yellow;
`
// In use
<MyComponent>
<MyChildComponent>A Goose!<MyChildComponent>
<MySubComponent>Click bait</MySubComponent>
<MyComponent>
Obviously there are situational reasons to mix and match these approaches, and I'm not taking into consideration use cases where a component may be re-used throughout a code base. I'm instead asking in the context of large chunks of markup that are unlikely to change or be shared.
reactjs styled-components
reactjs styled-components
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
asked Nov 20 '18 at 22:08
monnersmonners
3,96411940
3,96411940
In my experience, inverting the mapping ofstyles -> elementstoelements (components) -> stylesis invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors
– sliptype
Nov 20 '18 at 22:23
add a comment |
In my experience, inverting the mapping ofstyles -> elementstoelements (components) -> stylesis invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors
– sliptype
Nov 20 '18 at 22:23
In my experience, inverting the mapping of
styles -> elements to elements (components) -> styles is invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors– sliptype
Nov 20 '18 at 22:23
In my experience, inverting the mapping of
styles -> elements to elements (components) -> styles is invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors– sliptype
Nov 20 '18 at 22:23
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402341%2fstyled-components-nested-classname-selectors-vs-multiple-styled-components%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402341%2fstyled-components-nested-classname-selectors-vs-multiple-styled-components%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In my experience, inverting the mapping of
styles -> elementstoelements (components) -> stylesis invaluable when trying to reason about why certain styles are applying. In less complex situations this may not be so noticeable, but I still make it a point to avoid selectors– sliptype
Nov 20 '18 at 22:23