3scale/porta

View on GitHub
app/lib/three_scale/analytics/user_classifier.rb

Summary

Maintainability
A
0 mins
Test Coverage

ThreeScale::Analytics::UserClassifier#initialize is controlled by argument 'user'
Open

        @user = user || EMPTY_USER

Control Parameter is a special case of Control Couple

Example

A simple example would be the "quoted" parameter in the following method:

def write(quoted)
  if quoted
    write_quoted @value
  else
    write_unquoted @value
  end
end

Fixing those problems is out of the scope of this document but an easy solution could be to remove the "write" method alltogether and to move the calls to "writequoted" / "writeunquoted" in the initial caller of "write".

ThreeScale::Analytics::UserClassifier#is_guest? performs a nil-check
Open

        @user.username.nil? || @user.email.nil?

A NilCheck is a type check. Failures of NilCheck violate the "tell, don't ask" principle.

Additionally, type checks often mask bigger problems in your source code like not using OOP and / or polymorphism when you should.

Example

Given

class Klass
  def nil_checker(argument)
    if argument.nil?
      puts "argument isn't nil!"
    end
  end
end

Reek would emit the following warning:

test.rb -- 1 warning:
  [3]:Klass#nil_checker performs a nil-check. (NilCheck)

There are no issues that match your filters.

Category
Status