Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove className usage checker & suppression prop #2563

Merged
merged 3 commits into from May 29, 2019

Conversation

quantizor
Copy link
Contributor

It ends up creating a ton of dev noise in nextjs due to usage of React loadable and breaks things like React strict mode for which there is no current corollary.

Fixes #2154

@quantizor quantizor requested review from mxstbr and kitten May 29, 2019 03:05
Copy link
Member

@mxstbr mxstbr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, let's burn it with fire 🔥

@@ -74,7 +72,7 @@ class StyledComponent extends Component<*> {
// eslint-disable-next-line no-console
console.warn(
`Functions as object-form attrs({}) keys are now deprecated and will be removed in a future version of styled-components. Switch to the new attrs(props => ({})) syntax instead for easier and more powerful composition. The attrs key in question is "${key}" on component "${displayName}".`,
`\n ${(new Error()).stack}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why it was this way, maybe browser compat? Is this safe to change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

idk, prettier removed it so I assume a safe transform

@mxstbr mxstbr merged commit e3cefd9 into master May 29, 2019
@mxstbr mxstbr deleted the remove-className-checker branch May 29, 2019 08:15
@quantizor quantizor mentioned this pull request May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

React.StrictMode throws warning because of findDOMNode use
2 participants