sanger/sequencescape

View on GitHub
app/controllers/studies/information_controller.rb

Summary

Maintainability
A
2 hrs
Test Coverage
B
82%

Complex method Studies::InformationController#show_summary (88.9)
Open

  def show_summary # rubocop:todo Metrics/CyclomaticComplexity
    page_params = { page: params[:page] || 1, per_page: params[:per_page] || 50 }

    if request.xhr?
      @summary = params[:summary] || 'assets-progress'

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

Method show_summary has 33 lines of code (exceeds 25 allowed). Consider refactoring.
Open

  def show_summary # rubocop:todo Metrics/CyclomaticComplexity
    page_params = { page: params[:page] || 1, per_page: params[:per_page] || 50 }

    if request.xhr?
      @summary = params[:summary] || 'assets-progress'
Severity: Minor
Found in app/controllers/studies/information_controller.rb - About 1 hr to fix

    Complex method Studies::InformationController#show (30.3)
    Open

      def show # rubocop:todo Metrics/AbcSize, Metrics/MethodLength
        @summary = params[:summary] || 'sample-progress'
        @request_types = RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
        @summaries = BASIC_TABS + @request_types.pluck(:key, :name)
    
    

    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

    Method show_summary has a Cognitive Complexity of 9 (exceeds 5 allowed). Consider refactoring.
    Open

      def show_summary # rubocop:todo Metrics/CyclomaticComplexity
        page_params = { page: params[:page] || 1, per_page: params[:per_page] || 50 }
    
        if request.xhr?
          @summary = params[:summary] || 'assets-progress'
    Severity: Minor
    Found in app/controllers/studies/information_controller.rb - About 55 mins to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Studies::InformationController#show_summary has approx 19 statements
    Open

      def show_summary # rubocop:todo Metrics/CyclomaticComplexity

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

    Studies::InformationController has at least 12 instance variables
    Open

    class Studies::InformationController < ApplicationController

    Too Many Instance Variables is a special case of LargeClass.

    Example

    Given this configuration

    TooManyInstanceVariables:
      max_instance_variables: 3

    and this code:

    class TooManyInstanceVariables
      def initialize
        @arg_1 = :dummy
        @arg_2 = :dummy
        @arg_3 = :dummy
        @arg_4 = :dummy
      end
    end

    Reek would emit the following warning:

    test.rb -- 5 warnings:
      [1]:TooManyInstanceVariables has at least 4 instance variables (TooManyInstanceVariables)

    Studies::InformationController#show has approx 11 statements
    Open

      def show # rubocop:todo Metrics/AbcSize, Metrics/MethodLength

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

    Studies::InformationController#show calls '@study.submissions' 2 times
    Open

        @submissions = @study.submissions
        @awaiting_submissions = @study.submissions.where.not(state: 'ready')

    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.

    Studies::InformationController#show_summary calls '@study.requests.distinct.pluck(:request_type_id)' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#show_summary calls 'RequestType.where(id: @study.requests.distinct.pluck(:request_type_id))' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#show_summary calls 'RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#show_summary calls 'params[:summary]' 3 times
    Open

          @summary = params[:summary] || 'assets-progress'
    
          case @summary
          when 'sample-progress'
            @page_elements = @study.samples.paginate(page_params)

    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.

    Studies::InformationController#show_summary calls '@study.requests.distinct' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#show_summary calls 'RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#show_summary calls '@study.requests' 2 times
    Open

              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)
            render partial: 'sample_progress'
          when 'assets-progress'
            @request_types =
              RequestType.where(id: @study.requests.distinct.pluck(:request_type_id)).standard.order(:order, :id)

    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.

    Studies::InformationController#discover_study calls '@study.warnings' 2 times
    Open

        flash.now[:warning] = @study.warnings if @study.warnings.present?

    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.

    Studies::InformationController#summary has the variable name 's'
    Open

        s = UiHelper::Summary.new

    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