3scale/porta

View on GitHub

Showing 5,267 of 5,597 total issues

ThreeScale::Swagger::Specification::V10#validate! has the variable name 'e'
Open

          ops = apis.map{|e| e.nil? ? nil : e["operations"]}.flatten.compact
          ops.each do | operation |
            if operation["parameters"]
              paramTypes = operation["parameters"].map{|e| e["paramType"]}.compact

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.

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

    create_table :blog_posts do |t|
Severity: Minor
Found in db/migrate/018_create_blog_posts.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.

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

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

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

    create_table :tags do |t|
      t.column :name, :string
    end
    
    create_table :taggings 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.down has the variable name 't'
Open

    change_table :cinstances do |t|
      t.integer :backend_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.

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

    create_table :profiles do |t|
Severity: Minor
Found in db/migrate/003_create_profiles.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.

ThreeScale::OAuth2::Client::Options#to_hash has the variable name 'v'
Open

          { site: site, token_url: token_url, authorize_url: authorize_url, connection_opts: connection_opts }.reject { |_, v| !v }
Severity: Minor
Found in app/lib/three_scale/oauth2/client.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.

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

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

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

    change_table :metrics do |t|
      t.remove_belongs_to :contract
      t.belongs_to :service
    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.

ThreeScale::OAuth2 has the name 'OAuth2'
Open

  module OAuth2

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::OAuth2 has the name 'OAuth2'
Open

  module OAuth2

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.

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

    create_table :usagestats do |t|
Severity: Minor
Found in db/migrate/009_create_usagestats.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.

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

    create_table :cinstances do |t|
Severity: Minor
Found in db/migrate/012_create_cinstances.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.

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

    change_table :pricing_rules do |t|
      t.remove_belongs_to :contract
    end

    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.

ThreeScale::Swagger::Specification::V10 has the name 'V10'
Open

      class V10 < VBase

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.

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

    create_table :contracts_features, :id => false do |t|
      t.integer :contract_id
      t.integer :feature_id
    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.

RemoveObsolteColumnsFromContracts#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.

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

    change_table :services do |t|
      t.rename :title, :name
    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.

ChangeStateInContract#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.

ChangeStateInCinstance#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.

Severity
Category
Status
Source
Language