Fitbark::Data::Shared::ClassMethods has no descriptive comment Open
module ClassMethods
- Read upRead up
- Exclude checks
Classes and modules are the units of reuse and release. It is therefore considered good practice to annotate every class and module with a brief comment outlining its responsibilities.
Example
Given
class Dummy
# Do things...
end
Reek would emit the following warning:
test.rb -- 1 warning:
[1]:Dummy has no descriptive comment (IrresponsibleModule)
Fixing this is simple - just an explaining comment:
# The Dummy class is responsible for ...
class Dummy
# Do things...
end
Fitbark::Data::Shared#time_parser doesn't depend on instance state (maybe move it to another class?) Open
def time_parser(attr)
- Read upRead up
- Exclude checks
A Utility Function is any instance method that has no dependency on the state of the instance.
Fitbark::Data::Shared#init_breed doesn't depend on instance state (maybe move it to another class?) Open
def init_breed(attr)
- Read upRead up
- Exclude checks
A Utility Function is any instance method that has no dependency on the state of the instance.
Fitbark::Data::Shared#date_parser doesn't depend on instance state (maybe move it to another class?) Open
def date_parser(attr)
- Read upRead up
- Exclude checks
A Utility Function is any instance method that has no dependency on the state of the instance.
Fitbark::Data::Shared#init_medical_condition doesn't depend on instance state (maybe move it to another class?) Open
def init_medical_condition(attr)
- Read upRead up
- Exclude checks
A Utility Function is any instance method that has no dependency on the state of the instance.
Trailing whitespace detected. Open
- Exclude checks
Missing top-level module documentation comment. Open
module ClassMethods
- Read upRead up
- Exclude checks
This cop checks for missing top-level documentation of classes and modules. Classes with no body are exempt from the check and so are namespace modules - modules that have nothing in their bodies except classes, other modules, or constant definitions.
The documentation requirement is annulled if the class or module has a "#:nodoc:" comment next to it. Likewise, "#:nodoc: all" does the same for all its children.
Example:
# bad
class Person
# ...
end
# good
# Description/Explanation of Person class
class Person
# ...
end