Bug with automatic formatting for "function-paren-newline" rule

Tell us about your environment

• ESLint Version: 7.12.1
• Node Version: 14 LTS
• npm Version: 6

What parser (default, @babel/eslint-parser, @typescript-eslint/parser, etc.) are you using? default

Please show your full configuration:

Configuration

    "function-paren-newline": ["error", "multiline-arguments"],

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

self._debug(
  'error getting piece %s (offset: %s length: %s) from %s: %s',
  index, chunkOffset, chunkLength, `${wire.remoteAddress}:${wire.remotePort}`,
  err.message
)

What did you expect to happen?

I expected it to be formatted like this:

self._debug(
  'error getting piece %s (offset: %s length: %s) from %s: %s',
  index,
  chunkOffset,
  chunkLength,
  `${wire.remoteAddress}:${wire.remotePort}`,
  err.message
)

What actually happened? Please include the actual, raw output from ESLint.

self._debug(
  'error getting piece %s (offset: %s length: %s) from %s: %s',
  index,
  chunkOffset,
  chunkLength,
`${wire.remoteAddress}:${wire.remotePort}`,
err.message
)

Are you willing to submit a pull request to fix this bug?

Sorry, I don’t have time at the moment.

[ljharb]

With the indent rule enabled, wouldn’t that correct the latter example to your expected output?

[feross]

Great, then this is not an ESLint bug. Closing.