3scale/porta

View on GitHub

Showing 5,267 of 5,597 total issues

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

    change_table :contracts 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.

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

    change_table :contracts do |t|
      t.integer :position, :null => false, :default => 0
    end

    change_table :services 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.

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

    change_table :cinstances do |t|
      t.rename :sec_userkey, :user_key
      t.rename :sec_providerkey, :provider_public_key
      t.index :user_key, :unique => true
    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.

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

    change_table :usage_limits 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.

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

    change_table :contracts 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.

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

    change_table :contracts 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.

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

    change_table :transactions 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.

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

    change_table :invitations 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.

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

    change_table :settings 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.

ReportTrafficWorker#filter_request_attrs has the variable name 'v'
Open

        headers:   request.headers.select { |k, v| k =~ /HTTP_/ },
Severity: Minor
Found in app/workers/report_traffic_worker.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.

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

    change_table :cinstances 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.

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

    create_table :contract_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.

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

    create_table :slugs 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.

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

    change_table :profiles 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.

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

    change_table :reports 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.

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

    change_table :profiles do |t|
      t.string :viewstatus, :default => 'PRIVATE'
    end

    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.

UpgradeFriendlyIdTo20 has the name 'UpgradeFriendlyIdTo20'
Open

class UpgradeFriendlyIdTo20 < 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.

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

    create_table :themes 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.

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

    change_table :service_transactions 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.

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

    change_table :services do |t|
      t.remove :backend_service_id
    end

    change_table :contracts 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