Skip to content

Analyze aibolit report #303

@olenagerasimova

Description

@olenagerasimova

Let's analyze report (check this action) generated by aibolit and try to follow its recommendations to make our code better.
I'm proposing the following process:

  1. choose class from the report to work on,
  2. fix relevant problems and submit PR,
  3. report bugs (if any) to Aibolit,
  4. as for now there is no possibility to suppress bugs found by Aibolit, add comment here with small summary about the class you worked on: class name, problems left and why

Feel free to report any suggestion to Aibolit team and discuss any code related problems with me.

Do not close this issue when first PR is closed, I will close it when whole report by Aibolit is analyzed, or we will not need it anymore.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions