Showing 5,267 of 5,597 total issues
UsersHelper#link_to_login_with_IP has the name 'link_to_login_with_IP' Open
def link_to_login_with_IP content_text=nil, options={}
- 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.
Finance::Api::InvoicesController has the variable name 'k' Open
STATES = Hash.new {|_, k| k}.merge('cancel' => 'cancelled').freeze
- 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.
ApplicationController#status has the variable name 'e' Open
rescue ::Redis::BaseError => 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.
Admin::FieldsDefinitionsController#new has the variable name 'f' Open
current_account.fields_definitions.by_target(target).map{ |f|f.name }
- 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.
Admin::Api::CreditCardsController#update has the variable name 'e' Open
rescue ArgumentError => e
failed = "credit_card_expiration_month"
@buyer.errors.add(:credit_card_expires_on)
end
- 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.
Provider::Admin::Account::PaymentGateways::BraintreeBlueController#hack_errors has the variable name 'v' Open
current_account.billing_address.errors.messages.each do |k,v|
- 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.
Provider::Admin::Account::PaymentGateways::BraintreeBlueController#hack_errors has the variable name 'k' Open
current_account.billing_address.errors.messages.each do |k,v|
- 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::Data::BaseController#render_usage has the variable name 'e' Open
rescue Stats::InvalidParameterError => 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.
Provider::DomainsController#recover has the variable name 'p' Open
domains = site_account.managed_users.where(email: email_param).map{|p| p.account.external_admin_domain}.uniq
- 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::Api::BaseController#render_usage has the variable name 'e' Open
rescue Stats::InvalidParameterError => 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.
Dashboard::MessagesPresenter#t has the name 't' Open
def t(key)
- 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.
NotificationPreferencesForm#notification_categories has the variable name 'c' Open
category = ui_notification_categories.find { |c| c.title_key == ui_title_key }
- 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::Api::ServicesController#top_applications has the variable name 'e' Open
rescue Stats::InvalidParameterError => 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.
Stats::Data::ServicesController#top_applications has the variable name 'e' Open
rescue Stats::InvalidParameterError => 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.
ActionLimiter#perform has the variable name 'e' Open
rescue Redis::BaseError => 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.
Backend::ModelExtensions::Metric#self.included has the variable name 'm' Open
after_commit :sync_backend, if: ->(m) { (m.persisted? || m.destroyed?) && !m.changed? }
- 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.
TrafficService#last_traffic_date has the variable name 'i' Open
days_ago = usage.reverse.find_index{|i| i > 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.
AccessControl#self.included has the variable name 'e' Open
base.rescue_from CanCan::AccessDenied 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.
Provider::Admin::AuthenticationProvidersIndexPresenter#authentication_provider_kinds has the variable name 'a' Open
indexed.values.flatten.sort_by { |a| a.to_param.to_s }.reverse
- 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.
ExternalRssFeedPortlet#posts has the variable name 'p' Open
Nokogiri::XML(doc).xpath('//item').map do |p|
- 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.