3scale/porta

View on GitHub

Showing 5,267 of 5,597 total issues

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

    create_table :topic_categories, :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.

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

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

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

    change_table Plan.table_name do |t|
        t.boolean :approval_required, :null => false, :default => false
    end
    
    execute %{

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.

CreateCmsGroupsPermissions#self.up 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.

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

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

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

    change_table Service.table_name do |t|
      t.boolean :approval_required, :null => false, :default => false
    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.

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

    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.

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

    create_table "usage_limit_violations", :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.

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

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

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

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

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

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

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

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

RemoveOldViolations#self.up has the variable name 'v'
Open

      vios.each do |v|

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.

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

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

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

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

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

    create_table "monitorships", :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.

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

    create_table "releases", :force => true do |t|
      t.string   "name"
      t.string   "version"
      t.text     "notes"
      t.text     "quick_info"

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.

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

    Account.providers.find_each do |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.

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

    create_table "attachment_versions", :force => true do |t|
      t.integer  "attachment_id"
      t.integer  "version"
      t.string   "file_path"
      t.string   "file_location"

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.down 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.

Severity
Category
Status
Source
Language