[comma-dangle] Difference between function declaration and function call?

Just a suggestion, if it would make sense to have a difference for the function definition and function call? I’m asking that because sometimes it feels weird to have the comma. Especially in function which takes an arrow function.

something.map(url =>
  sthelse
);

With the rule enabled with multiline, it asks a comma after sthelse. Would it be possible to have an option to not do it? Would it make sense?

This is particularly weird when playing with jsx.

const component = renderer.create(
  <ESLintItem>
    <a href="http://eslint.org">ESLint</a>
  </ESLintItem>,
);

[ljharb]

@johntran the airbnb config requires trailing commas on function arguments.

Indeed, your arrow function, and @cmalard, your console.log argument, need trailing commas. It is indeed valid JS, it’s just ES2017. The airbnb config expects you’re using https://npmjs.com/babel-preset-airbnb

[msmichellegar]

I was just reporting the same issue as you commented @ljharb. Thanks!