Stance on React 0.14 stateless function components

[jaroslawr]

The React part of the coding standard, with its insistence of using classes for components, when read literally seems to be prohibiting the now officially recommended stateless function components:

var Aquarium = ({species}) => (
  <Tank>
    {getFish(species)}
  </Tank>
);

https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html

I guess this was just written before React 0.14. Any chances of taking some more explicit stance on those in the coding standard?

[goatslacker]

We don't use React 0.14 just quite yet so we don't have a stance on it.

If you're just looking for opinions then I believe that stateless function components should make up a vast majority of your components therefore I'd use those over React.createClass and extends React.Component.

[justjake]

I agree with @goatslacker - stateless functional components are fantastic, and once we upgrade to 0.14 we'll upgrade our styleguide to extol their virtues.

[jacobrask]

Maybe the linter could even suggest to use a stateless functional component if no lifecycle methods or component state is used?

[goatslacker]

Can't we close this? Is there more work that needs to be done here?

@jacobrask that seems like a feature request for eslint-react

[ljharb]

I think #575 clarifies our stance.

I filed jsx-eslint/eslint-plugin-react#405 for that feature request. We'll also need jsx-eslint/eslint-plugin-react#357 and jsx-eslint/eslint-plugin-react#354.

[ljharb]

Linking to jsx-eslint/eslint-plugin-react#214 instead of jsx-eslint/eslint-plugin-react#405