warn users when allegedly "themed" styles dont use themes.

[iamstarkov]

Is your feature request related to a problem? Please describe.

Sometimes developers define styles as themed once purely out of habit without real necessity to depend on a theme.

export const styles = () => ({
  root: {},
});

Apparently people do it a lot.

Describe the solution you'd like
When component pulls this trick please warn developer this component doesn't need to use themed styles.

Are you willing to implement it?
Yes

[HenriBeck]

You can do it with fn.length:

function styles(test) {}

console.log(styles.length);

https://codesandbox.io/s/zx0l4p527p

[kof]

Thats quite easy to add.

[HenriBeck]

We could even do the same with function styles in development so that they also only receive one argument.

We should warn when the user uses anything other than one argument.

[kof]

Yeah

[iamstarkov]

is master branch a proper branch to base PR on?

[HenriBeck]

yes

[iamstarkov]

I'm on it then

[iamstarkov]

offtopic question. why author field in react-css is the way it is?

   "author": {
    "name": "Dan Abramov",
    "email": "[email protected]"
  },

[kof]

@gaearon has originally created the first version of react-jss. I am not sure what the traditions are around author field, it has been obviously rewritten several times since then.

[HenriBeck]

I think we should make the author field something which points to our repo and contributors.

Also, it should be the same for every package in my opinion.