I know this is not controversial so I am going to ship it in standard 14. No ecosystem repos fail.

@feross Doesn't this collide with indent/jsx-indent rule?

@MatanBobi I don't believe so. Can you explain how?

@feross I think that @MatanBobi means using non-self-closing tag with return:

  render () {
    return <div>
      Closing tag below where should be?
    </div>
  }

With this rule, this style raises an error (not aligned to open tag) and if I try to --fix it:

  render () {
    return <div>
      Closing tag below where should be?
           </div>
  }

which raises react/jsx-indent-problem and is ugly.

The only way to fix it is putting all in one line:

  render () {
    return <div>Closing tag below where should be?</div>
  }

but is not really sustainable.

@joke2k The intended style is to add parens anytime you have a multiline JSX statement.

  render () {
    return (
      <div>
        Closing tag below where should be?
      </div>
    )
  }

I'm not sure why the autofixer isn't doing that for you. Looks like we need to play with the JSX rules some more to get what we want.

Re-opening so we can investigate fixing this for standard 15. Help wanted!

@joke2k You got exactly what I meant, thanks for the wide explanation.

I believe this is fixed in standard 16.