remove the local variable and return the result directly

[xuejiangtao]

I found a code smell that Local Variables should not be declared and then immediately returned or thrown.
Some developers argue that the practice improves code readability, because it enables them to explicitly name what is being returned. However, this variable is an internal implementation detail that is not exposed to the callers of the method. The method name should be sufficient for callers to know exactly what will be returned.

So I remove the local variable and return the personMapper.count(selectStatement); directly to fix the Code Quality Issue detected by SonarQube.
https://rules.sonarsource.com/java/RSPEC-1488

[coveralls]

Coverage remained the same at 100.0% when pulling e96a77b on xuejiangtao:master into 79513eb on mybatis:master.

[xuejiangtao]

@jeffgbutler hello, I found a code smell that Local Variables should not be declared and then immediately returned or thrown.
Some developers argue that the practice improves code readability, because it enables them to explicitly name what is being returned. However, this variable is an internal implementation detail that is not exposed to the callers of the method. The method name should be sufficient for callers to know exactly what will be returned.

So I remove the local variable and return the personMapper.count(selectStatement); directly to fix the Code Quality Issue detected by SonarQube.
https://rules.sonarsource.com/java/RSPEC-1488

[jeffgbutler]

Thanks!

[xuejiangtao]

Thanks!

thanks for reviewing and i will do some contributions to improve the Code Quality with fix patch generated by my tool