3scale/porta

View on GitHub

Showing 5,267 of 5,597 total issues

CreateLegalTermBindings#self.up has the variable name 't'
Open

    create_table :legal_term_bindings do |t|

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.

AddCmsTemplatesVersions#self.up has the variable name 't'
Open

    change_table :cms_templates_versions do |t|

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.

CreateAccountAndServicePlans#self.up has the variable name 'p'
Open

    Account.providers.find_each { |p| add_plans_to_provider(p) }

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.

CreatePlanMetrics#self.up has the variable name 't'
Open

    create_table :plan_metrics do |t|

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.

CreateWebHooks#self.up has the variable name 't'
Open

    create_table :web_hooks do |t|

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.

DumpingUnusedTables#self.down has the variable name 't'
Open

    create_table "credit_transactions", :force => true do |t|
      t.integer  "account_id"
      t.string   "kind",                                                 :default => "incoming"
      t.string   "currency",                                             :default => "EUR",      :null => false
      t.decimal  "amount",                :precision => 10, :scale => 2, :default => 0.0,        :null => false

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.

TurnOffNewForumPostDispatchRule#self.up has the variable name 'm'
Open

      MailDispatchRule.find(:all, :conditions => ["system_operation_id = ?", operation.id]).each do |m|

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.

CreateLegalTerms#self.up has the variable name 't'
Open

    create_table :legal_terms do |t|
      t.string :name
      t.string :slug
      t.text :body
      t.integer :version

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.

RemoveTestAttributeFromPlans#self.up has the variable name 't'
Open

    change_table Plan.table_name do |t|

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.

DroppingUsageLineItems#self.down has the variable name 't'
Open

    create_table "usage_line_items", :force => true do |t|

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.

DroppingApplicationsAndApplicationTokens#self.down has the variable name 't'
Open

    create_table "applications", :force => true do |t|
      t.integer "account_id"
      t.string  "name"
      t.text    "description"
    end

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.

DropCmsGroupsPermission#self.down has the variable name 't'
Open

    create_table :cms_groups_permissions do |t|

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.

CreateGoLiveStates#change has the variable name 't'
Open

    create_table :go_live_states do |t|

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.

ConvertNotificationsToUtf8 has the name 'ConvertNotificationsToUtf8'
Open

class ConvertNotificationsToUtf8 < ActiveRecord::Migration

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.

AddProductEnterpriseToMaster#self.up has the variable name 'm'
Open

    m = Account.master

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.

AddProxyConfigsToProvider#self.up has the variable name 't'
Open

    change_table :accounts do |t|

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.

AddSupportEmailsToAccounts#self.down has the variable name 'a'
Open

    change_table :accounts do |a|

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.

AddSupportEmailToServices#self.up has the variable name 's'
Open

    change_table :services do |s|

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.

SystemNameUniqueIndex#self.up has the variable name 'r'
Open

      model.find_each do |r|

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.

CreateProxyRules#self.up has the variable name 't'
Open

    create_table :proxy_rules do |t|

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.

Severity
Category
Status
Source
Language