Showing 65 of 125 total issues
Rectify::RSpec::DatabaseReporter::QueryStats#initialize has the variable name 'h' Open
@stats = Hash.new { |h, k| h[k] = [] }
- Read upRead up
- Exclude checks
An Uncommunicative Variable Name
is a variable name that doesn't communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what's going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.
Rectify::Form#attributes_that_respond_to has the variable name 'f' Open
.select { |f| f.respond_to?(message) }
- Read upRead up
- Exclude checks
An Uncommunicative Variable Name
is a variable name that doesn't communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what's going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.
Rectify::Query#self.merge has the variable name 'a' Open
queries.reduce(NullQuery.new) { |a, e| a.merge(e) }
- Read upRead up
- Exclude checks
An Uncommunicative Variable Name
is a variable name that doesn't communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what's going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.
Rectify::RSpec::DatabaseReporter::QueryStats#initialize has the variable name 'k' Open
@stats = Hash.new { |h, k| h[k] = [] }
- Read upRead up
- Exclude checks
An Uncommunicative Variable Name
is a variable name that doesn't communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what's going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.
Rectify::FormatAttributesHash#underscore_key has the parameter name 'k' Open
def underscore_key(k)
- Read upRead up
- Exclude checks
An Uncommunicative Parameter Name
is a parameter name that doesn't communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what's going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.