Sign upLogin

3scale/porta

View on GitHub
Star

Showing 5,267 of 5,597 total issues

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

    change_table :services do |t|
Severity: Minor
Found in db/migrate/20080822082807_change_state_in_services.rb by reek

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.

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

    change_table :accounts do |t|
Severity: Minor
Found in db/migrate/20081024155910_change_default_currency_to_eur_in_accounts.rb by reek

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.

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

    create_table :exchange_rates, :force => true do |t|
Severity: Minor
Found in db/migrate/20081024180108_create_exchange_rates.rb by reek

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.

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

    Service.all.each do |s|
Severity: Minor
Found in db/migrate/20081205122455_add_parent_id_to_services.rb by reek

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.

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

    change_table :settings do |t|
Severity: Minor
Found in db/migrate/20090327114631_add_payments_enabled_to_settings.rb by reek

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.

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

    create_table :line_items do |t|
Severity: Minor
Found in db/migrate/20090608135336_create_line_items.rb by reek

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.

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

    change_table :cinstances do |t|
      t.remove_index :user_key
      t.rename :user_key, :sec_userkey
      t.rename :provider_key, :sec_providerkey 
    end
Severity: Minor
Found in db/migrate/20080725075118_change_keys.rb by reek

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.

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

    change_table :services do |t|
Severity: Minor
Found in db/migrate/20080822082807_change_state_in_services.rb by reek

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.

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

    change_table :tags do |t|
Severity: Minor
Found in db/migrate/20080831181227_add_parent_to_tags.rb by reek

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.

CreateSettingsObjectForAccounts#self.up has the variable name 'a'
Open

    Account.with_deleted.all.each do |a|
Severity: Minor
Found in db/migrate/20090206174052_create_settings_object_for_accounts.rb by reek

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.

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

    create_table :downloads do |t|
Severity: Minor
Found in db/migrate/20100211142311_create_downloads.rb by reek

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.

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

    change_table :contracts do |t|
Severity: Minor
Found in db/migrate/20080731075548_remove_obsolte_columns_from_contracts.rb by reek

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.

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

    change_table :accounts do |t|
Severity: Minor
Found in db/migrate/20080805124622_add_balances_to_account.rb by reek

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.

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

    create_table :contracts_metrics, :id => false do |t|
      t.integer :contract_id
      t.integer :metric_id
    end
Severity: Minor
Found in db/migrate/20080820084058_kill_obsolete_stuff.rb by reek

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.

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

    change_table :cinstances do |t|
Severity: Minor
Found in db/migrate/20080822140627_change_state_in_cinstance.rb by reek

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.

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

    change_table :contracts do |t|
      t.string :currency, :default => 'EUR'
    end

    change_table :accounts do |t|
Severity: Minor
Found in db/migrate/20080825105417_add_currency_to_account.rb by reek

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.

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

    change_table :accounts do |t|
      t.string :currency
    end

    change_table :contracts do |t|
Severity: Minor
Found in db/migrate/20080825105417_add_currency_to_account.rb by reek

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.

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

     create_table :messages do |t|
      t.references :sender, :polymorphic => true, :null => false
      t.text :subject
      t.text :body
      t.string :state, :null => false
Severity: Minor
Found in db/migrate/20080922155721_has_messages_to_version_2.rb by reek

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.

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

    change_table :services do |t|
Severity: Minor
Found in db/migrate/20080930100356_add_approval_required_to_services.rb by reek

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.

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

    create_table :audits, :force => true do |t|
Severity: Minor
Found in db/migrate/20081007104553_add_audits_table.rb by reek

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