Showing 5,267 of 5,597 total issues
Stats::Storage#compute_timeshift_deltas has the variable name 'i' Open
mget(*keys).in_groups_of(margin.count).map do |i|- 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.
Stats::Storage#timeshift_values_by_deltas has the variable name 'i' Open
values.map do |value, i|
current_delta = deltas.fetch(i, 0)
next_delta = deltas.fetch(i+1, 0)
if shift > 0- 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.
ThreeScale::OAuth2 has the name 'OAuth2' Open
module OAuth2- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
Stats::Storage#granularity_to_hours has the parameter name 'g' Open
def granularity_to_hours(g)- 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.
Stats::Views::Usage#extract_range_and_granularity has the variable name 'e' Open
rescue ThreeScale::HashHacks::MissingKeyError => 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.
ThreeScale::OAuth2 has the name 'OAuth2' Open
module OAuth2- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
ThreeScale::PrivateModule#PrivateModule#self.append_features has the variable name 'm' Open
@mods.each do |m|- 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.
ThreeScale::Swagger::Specification::V12 has the name 'V12' Open
class V12 < VBase- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
ThreeScale::Swagger::Translator#self.translate! has the variable name 't' Open
stages.map{|t| translator.send("#{t}_translator".to_sym)}- 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.
ThreeScale::OAuth2::GitHubClient#primary_email has the variable name 'i' Open
primary = emails.find{ |i| i['primary'] && i['verified'] }- 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.
ThreeScale::OAuth2 has the name 'OAuth2' Open
module OAuth2- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
SendUserInvitationWorker has the variable name 'e' Open
rescue_from ActiveJob::DeserializationError do |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.
NotificationMailer has the variable name 'h' Open
self.event_mapping = 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.
ThreeScale::SSO::Encryptor#extract! has the variable name 't' Open
generation_time, expiration_time = raw.map{ |t| Time.at(t.to_f) }- 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.
ThreeScale::OAuth2 has the name 'OAuth2' Open
module OAuth2- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
ProcessNotificationEventWorker#create_notifications has the variable name 'e' Open
rescue ActiveRecord::RecordNotFound => 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.
CreateContracts#self.up has the variable name 't' Open
create_table :contracts do |t|- 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.
ThreeScale::Swagger::Translator#operations has the variable name 'w' Open
@_ops ||= swagger.fetch('apis',[]).flat_map{ |w| w['operations'] }.compact- 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.
ThreeScale::OAuth2 has the name 'OAuth2' Open
module OAuth2- Read upRead up
- Exclude checks
An Uncommunicative Module Name is a module 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.
ThreeScale::PrivateModule#PrivateModule has the name 'PrivateModule' Open
def PrivateModule(*modules)- Read upRead up
- Exclude checks
An Uncommunicative Method Name is a method 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.