4 Matching Annotations
- Sep 2020
-
github.com github.com
-
The RFC is more appropriate because it does not allow a parent to abritrarily control anything below it, that responsibility still relies on the component itself. Just because people have been passing classes round and overriding child styles for years doesn't mean it is a good choice and isn't something we wnat to encourage.
-
margin, flex, position, left, right, top, bottom, width, height, align-self, justify-self among other is CSS properties that should never be modified by the child itself. The parent should always have control of those properties, which is the whole reason I'm asking for this.
Tags
- who should have control over this? (programming)
- programming: who is responsible for this concern?
- which component/tool/organization/etc. is responsible for this concern?
- constraints are helpful
- Svelte: components are their own boss (encapsulation)
- control (programming)
- whose responsibility is it?
- limiting how much library consumers/users can control/override
Annotators
URL
-
-
github.com github.com
-
Often, allowing the parents to compose elements to be passed into components can offer the flexibility needed to solve this problem. If a component wants to have direct control over every aspect of a component, then it should probably own the markup as well, not just the styles. Svelte's slot API makes this possible. You can still get the benefits of abstracting certain logic, markup, and styles into a component, but, the parent can take responsibility for some of that markup, including the styling, and pass it through. This is possible today.
-
- Aug 2019
-
medium.com medium.com
-
I was so fed up of the mega amounts of boilerplate with Redux and the recommendation of keeping your data loading at view level. It seems to me that things like this, with components being responsible for their own data, is the way to go in the future.
-