Make error span first line only for arrow functions with expression body #60809
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #57866.
(In addition to #60799, this is only one part of #57866. It doesn't completely fix the issue.)
This should make the error span less noisy.
We were already doing this for block bodies, and I don't see any reason why we wouldn't also do it for non-block bodies. In my experience it's very common to have long multi-line non-block arrow functions, especially when using the
pipe
function.I'm also considering whether these errors should only span
=>
orreturn
, but that's a bigger change.