styled-components/styled-components
### [`v5.1.0`](https://togithub.com/styled-components/styled-components/blob/master/CHANGELOG.md#v510---2020-04-07)
[Compare Source](https://togithub.com/styled-components/styled-components/compare/v5.0.1...v5.1.0)
##### New Functionality
- Add `shouldForwardProp` API (almost the same as emotion's, just a slightly different usage pattern); [#3006](https://togithub.com/styled-components/styled-components/pull/3006)
Sometimes when composing multiple higher-order components together, it's possible to get into scenarios when multiple layers consume props by the same name. In the past we've introduced various workarounds for popular props like `"as"` but this power-user API allows for more granular customization of what props are passed down to descendant component children when using the `styled()` HOC wrapper.
When combined with other APIs like `.attrs()` this becomes a very powerful constellation of abilities.
Here's how you use it:
```jsx
const Comp = styled('div').withConfig({
shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop),
})`
color: red;
`;
render();
```
Renovate configuration
:date: Schedule: "on the first day of the month" (UTC).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
^5.0.1->^5.1.0Release Notes
styled-components/styled-components
### [`v5.1.0`](https://togithub.com/styled-components/styled-components/blob/master/CHANGELOG.md#v510---2020-04-07) [Compare Source](https://togithub.com/styled-components/styled-components/compare/v5.0.1...v5.1.0) ##### New Functionality - Add `shouldForwardProp` API (almost the same as emotion's, just a slightly different usage pattern); [#3006](https://togithub.com/styled-components/styled-components/pull/3006) Sometimes when composing multiple higher-order components together, it's possible to get into scenarios when multiple layers consume props by the same name. In the past we've introduced various workarounds for popular props like `"as"` but this power-user API allows for more granular customization of what props are passed down to descendant component children when using the `styled()` HOC wrapper. When combined with other APIs like `.attrs()` this becomes a very powerful constellation of abilities. Here's how you use it: ```jsx const Comp = styled('div').withConfig({ shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop), })` color: red; `; render(Renovate configuration
:date: Schedule: "on the first day of the month" (UTC).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.