This repository was archived by the owner on Jul 16, 2023. It is now read-only.
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.
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix
[x] New rule
[ ] Changes an existing rule
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
#474
Is there anything you'd like reviewers to focus on?
The fixer implemented is something like "semi-automatic" fixer, it does only half of the work required :) It replaces only expression in the problematic return statement and code contains unused variable after that.
For example,
will be fixed as
and
sum
variable should be manually removed. I think that this shoud be acceptable - it's not a huge amount of work to manually remove unused variable (linters should warn about it too).Implementing fully automatic fixer seems to be a bit hard: we have to replace multiple nodes/statements, but currently (as I see) we have only
nodeLocation
utility method which can create location only from single node.