More lenient jsx-no-multiline-js rule

I think the rule should be lenient about these kinds of multiline expressions because they don’t hinder readability too much:

update: we should also add more exemptions:

• allow-function-call to ignore function call expressions
• allow-literal to ignore checking object and array literals
• allow-element to ignore JSX elements

[pingshunhuang]

@adidahiya Could you please recommend a way for the 2 cases you gave above. I got this rules triggered a lot and I’m not sure how to improve them. Thanks.

[adidahiya]

@MiguelMadero eh, that wouldn’t really solve my use case because so much of JS syntax is a valid expression. My primary motivation for using this rule was to ban multiline ternarys and function calls (primarily .map, since it’s used to generate lists)

// bad
<div className={
    someComplicatedCondition
        ? "positive-case"
        : "positive-case"}
    otherProp={true}
/>

// bad
<div>
    {this.props.foo.map((f) => {
        return <span>{f}</span>;
    })}
</div>

I could imagine another option here for stylistic preference, however, ignore-conditional-expressions, to allow multiline ternarys like in my first example ^