sanger/sequencescape

View on GitHub
app/controllers/bulk_submissions_controller.rb

Summary

Maintainability
A
0 mins
Test Coverage
A
100%

Complex method BulkSubmissionsController#create (27.7)
Open

  def create # rubocop:todo Metrics/AbcSize
    begin
      @bulk_submission = BulkSubmission.new(params.fetch(:bulk_submission, {}))
      if @bulk_submission.valid?
        flash.now[:notice] = 'File was processed successfully'

Flog calculates the ABC score for methods. The ABC score is based on assignments, branches (method calls), and conditions.

You can read more about ABC metrics or the flog tool

BulkSubmissionsController#create has approx 10 statements
Open

  def create # rubocop:todo Metrics/AbcSize

A method with Too Many Statements is any method that has a large number of lines.

Too Many Statements warns about any method that has more than 5 statements. Reek's smell detector for Too Many Statements counts +1 for every simple statement in a method and +1 for every statement within a control structure (if, else, case, when, for, while, until, begin, rescue) but it doesn't count the control structure itself.

So the following method would score +6 in Reek's statement-counting algorithm:

def parse(arg, argv, &error)
  if !(val = arg) and (argv.empty? or /\A-/ =~ (val = argv[0]))
    return nil, block, nil                                         # +1
  end
  opt = (val = parse_arg(val, &error))[1]                          # +2
  val = conv_arg(*val)                                             # +3
  if opt and !arg
    argv.shift                                                     # +4
  else
    val[0] = nil                                                   # +5
  end
  val                                                              # +6
end

(You might argue that the two assigments within the first @if@ should count as statements, and that perhaps the nested assignment should count as +2.)

BulkSubmissionsController#create calls 'flash.now' 3 times
Open

        flash.now[:notice] = 'File was processed successfully'
        sub_ids, @sub_details = @bulk_submission.completed_submissions
        @these_subs = Submission.find(sub_ids)
      else
        flash.now[:error] = 'There was a problem with your upload'

Duplication occurs when two fragments of code look nearly identical, or when two fragments of code have nearly identical effects at some conceptual level.

Reek implements a check for Duplicate Method Call.

Example

Here's a very much simplified and contrived example. The following method will report a warning:

def double_thing()
  @other.thing + @other.thing
end

One quick approach to silence Reek would be to refactor the code thus:

def double_thing()
  thing = @other.thing
  thing + thing
end

A slightly different approach would be to replace all calls of double_thing by calls to @other.double_thing:

class Other
  def double_thing()
    thing + thing
  end
end

The approach you take will depend on balancing other factors in your code.

BulkSubmissionsController#create calls 'render action: 'new'' 2 times
Open

        render action: 'new'
      end
    rescue ActiveRecord::RecordInvalid => e
      flash.now[:error] = 'There was a problem when building your submissions'
      @bulk_submission.errors.add(:base, e.message)

Duplication occurs when two fragments of code look nearly identical, or when two fragments of code have nearly identical effects at some conceptual level.

Reek implements a check for Duplicate Method Call.

Example

Here's a very much simplified and contrived example. The following method will report a warning:

def double_thing()
  @other.thing + @other.thing
end

One quick approach to silence Reek would be to refactor the code thus:

def double_thing()
  thing = @other.thing
  thing + thing
end

A slightly different approach would be to replace all calls of double_thing by calls to @other.double_thing:

class Other
  def double_thing()
    thing + thing
  end
end

The approach you take will depend on balancing other factors in your code.

BulkSubmissionsController#create has the variable name 'e'
Open

    rescue ActiveRecord::RecordInvalid => e

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.

BulkSubmissionsController#find_submission_template_groups has the variable name 't'
Open

      SubmissionTemplate.visible.include_product_line.group_by 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.

There are no issues that match your filters.

Category
Status