func-names causes visual clutter inside editors

[xsrvmy]

The func-names rule flags the entire function instead of just the declaration, causing visual clutter in editors such as VSCode.

What rule do you want to change?
func-names

Does this change cause the rule to produce more or fewer warnings?
No

How will the change be implemented? (New option, new default behavior, etc.)?
Either new option, or change current behaviour.

Please provide some example code that this change will affect:

const x = function () {
  return 100;
}

What does the rule currently do for this code?
Highlights the entire function declaration as a warning.

What will the rule do after it's changed?
Highlight only function () .

Are you willing to submit a pull request to implement this change?
Maybe

[platinumazure]

Hi @xsrvmy, thanks for the issue.

I think this is a great idea. I will champion this change.

[kaicataldo]

One thing we should account for when we actually implement this is the potential for return types (I think they should be highlighted as well).

[mysticatea]

For reference, we have a utility, getFunctionHeadLoc().

[g-plane]

I think there's no need to add a new option.

[platinumazure]

Since I both championed and 👍'd this issue, I think we need one more team member in order to accept. (I have removed my 👍 to reduce confusion.)

@eslint/eslint-team Could we get one more 👍 for this issue? This is just to adjust the reporting range for editor integrations.

[aladdin-add]

here is the 3rd 👍 , labelled accepted.