fixed boolean getters recognition, improved performance #24
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.
By convention, accessors to boolean fields are generated with
is
prefix. If getter withget
method is not found, try to find one withis
prefix.Some performance fix was made with assumption that most getters and setters have public visibility. In this case it is faster to call
Class.getMethod
method which searches for method defined in parent classes and works about 30 per cent faster (see the benchmark).If number of methods defined in target class is small, it may be faster to call
Class.getDeclaredMethods()
and check method name and arguments (but I didn't implement this algorithm)