This repository has been archived by the owner on Nov 3, 2024. It is now read-only.
Only delete getters that have the canonical form #726
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.
#688
This is just a proof of concept, to get some early feedback.
Of course the same work would have to be done for the setters as well.
And maybe for the equals and hashCode methods. It might get trickier to test whether these are of the few established standard forms, as produced by Eclipse, IntelliJ and a few other IDEs.
My main focus are the getters and setters for now since manually checking for typos in that code is absolutely boring and error-prone.
While testing I noticed that Lombok will add a getter for
fieldWithoutGetter
. This may be intentional or not.