We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to #2, it would be nice to have a rule that enforces the inverse: using styles that are not defined.
Bad:
function MyComponent({ styles }) { return ( <div {...css(styles.foo, styles.bar)}> Foo </div> ); } export default withStyles(() => ({ foo: { backgroundColor: 'red', }, }))(MyComponent);
Good:
function MyComponent({ styles }) { return ( <div {...css(styles.foo, styles.bar)}> Foo </div> ); } export default withStyles(() => ({ foo: { backgroundColor: 'red', }, bar: { color: 'white', }, }))(MyComponent);
The text was updated successfully, but these errors were encountered:
This seems very aspirational - especially if MyComponent is defined in a different file than the HOC.
MyComponent
Sorry, something went wrong.
I think a 90% solution is better than none.
No branches or pull requests
Similar to #2, it would be nice to have a rule that enforces the inverse: using styles that are not defined.
Bad:
Good:
The text was updated successfully, but these errors were encountered: