reek 6.0.3 → 6.0.4

data/docs/Duplicate-Method-Call.md

@@ -1,264 +0,0 @@
-# Duplicate Method Call
-
-## Introduction
-
-Duplication occurs when two fragments of code look nearly identical, or when two fragments of code have nearly identical effects at some conceptual level.
-
-Let's look at an example that is quite common in the Rails world:
-
-```Ruby
-def not_production?
-  Rails.env.development? || Rails.env.test?
-end  
-```
-
-While this duplicate usage of `Rails.env` might seem innocuous there are 2 problems with it:
-
-1.) Efficiency
-
-```Ruby
-Rails.env.development? || Rails.env.test?
-```
-
-is not as efficient as it could be. If the call to `env` is not memoized your basically paying twice in terms of computation for something that you should only pay once.
-
-Here
-
-```Ruby
-Rails.env.development? || Rails.env.test?
-```
-
-you have 4 method calls while here:
-
-```Ruby
-env = Rails.env
-env.development? || env.test?
-```
-
-you have one assignment (which is very cheap in terms of computation) and 3 method calls.
-The difference might not be much here but just imagine you're writing a high performance app or you doing some expensive database calls in each method call.
-
-It doesn't really matter though if the efficiency difference is significant. This is a matter of principle - we believe that being efficient is one of the vital traits of good software.
-
-2.) Maintainability
-
-The second point is a bit more subtle. This
-
-```Ruby
-env = Rails.env
-env.development? || env.test?
-```
-
-is a lot more intention revealing than 
-
-```Ruby
-Rails.env.development? || Rails.env.test?
-```
-
-Here
-
-```Ruby
-env = Rails.env
-env.development? || env.test?
-```
-
-I'm very clear on what I do: I get the environment and then I run some checks on it.
-
-Here
-
-```Ruby
-Rails.env.development? || Rails.env.test?
-```
-
-I'm not very clear on what I do and it requires quite more mental effort: Ok, so I'm talking to Rails, getting the environment and then running a check on it ...or .....oh, I get the same Rails constant again, get the same environment and run another check on it.
-
-## Example
-
-Here's a very much simplified and contrived example. The following method will report a warning:
-
-```Ruby
-def double_thing
-  @other.thing + @other.thing
-end
-```
-
-One quick approach to silence Reek would be to refactor the code thus:
-
-```Ruby
-def double_thing
-  thing = @other.thing
-  thing + thing
-end
-```
-
-A slightly different approach would be to replace all calls in `double_thing` by calls to `thing`:
-
-```Ruby
-class Other
-  def double_thing
-    thing + thing
-  end
-
-  def thing
-    @other.thing
-  end
-end
-```
-
-The approach you take will depend on balancing other factors in your code.
-
-## Current support in Reek
-
-Reek's Duplicate Method Call detector checks for repeated identical method calls within
-any one method definition. This is intended to complement the checks performed by tools
-such as [Flay](http://ruby.sadi.st/Flay.html) and [Simian](http://www.redhillconsulting.com.au/products/simian/).
-
-## Edge cases
-
-Be aware that there are some edge cases like this code:
-
-```Ruby
-class Foo
-  def bar(switch)
-    case switch
-    when :a
-      ->(arg) { arg.call_me(:maybe); do_something }
-    when :b
-      ->(arg) { arg.call_me(:maybe); do_something_else }
-    when :c
-      ->(arg) { arg.call_me(:maybe); do_something_different }
-    end
-  end
-end
-```
-
-Reek cannot reliably detect that each call's receiver is a different arg and will report:
-
-```
-[5, 7, 9]:DuplicateMethodCall: Foo#bar calls 'arg.call_me(:maybe)' 3 times
-```
-  
-If you're running into this problem you can disable this smell detector for this method either via
-configuration:
-
-```Yaml
----
-DuplicateMethodCall:
-  exclude:
-    - 'Foo#bar'
-```
-
-or via source code comment:
-
-```Ruby
-class Foo
-  # :reek:DuplicateMethodCall
-  def bar(switch)
-    # ....
-  end
-end
-```
-
-## Configuration
-
-Reek's Duplicate Method Call detector currently offers the [Basic Smell Options](Basic-Smell-Options.md), plus:
-
-Option | Value | Effect
--------|-------|-------
-`max_calls` |  integer | The maximum number of duplicate calls allowed within a method. Defaults to 1.
-`allow_calls` | an array of strings or regular expressions | Ignores any context who matches it |
-
-## Example configuration
-
-### Adjusting `max_calls`
-
-Imagine code like this:
-
-```Ruby
-class Alfa
-  def bravo
-    charlie.delta
-    charlie.delta
-  end
-end
-```
-
-This would report:
-
->>
-src.rb -- 1 warning:
-  [4, 5]:DuplicateMethodCall: Alfa#bravo calls 'charlie.delta' 2 times
-
-If you want to allow those double calls here you can disable it in 2 different ways:
-
-1.) Via source code comment:
-
-```Ruby
-class Alfa
-  # :reek:DuplicateMethodCall { max_calls: 2 }
-  def bravo
-    charlie.delta
-    charlie.delta
-  end
-end
-```
-
-2.) Via configuration file:
-
-```Yaml
-DuplicateMethodCall:
-  max_calls: 2
-```
-
-Note though that the latter way will set `max_calls` to 2 for all instances
-of the smell detector which might not be what you want - in this case
-you'll have to use source code comments.
-
-### Adjusting `allow_calls`
-
-Imagine code like this:
-
-```Ruby
-class Alfa
-  def bravo
-    charlie.delta
-    charlie.delta
-    echo.foxtrot
-    echo.foxtrot
-  end
-end
-```
-
-This would report:
-
->>
-src.rb -- 2 warnings:
-  [4, 5]:DuplicateMethodCall: Alfa#bravo calls charlie.delta 2 times
-  [6, 7]:DuplicateMethodCall: Alfa#bravo calls echo.foxtrot 2 times
-
-So let's say you're ok with the `echo.foxtrot` calls you can stop reporting them like this:
-
-1.) Via source code comment:
-
-```Ruby
-class Alfa
-  # :reek:DuplicateMethodCall { allow_calls: ['echo.foxtrot'] }
-  def bravo
-    charlie.delta
-    charlie.delta
-    echo.foxtrot
-    echo.foxtrot
-  end
-end
-```
-
-2.) Via configuration file:
-
-```Yaml
-DuplicateMethodCall:
-  allow_calls:
-  - 'echo.foxtrot'
-```
-
-Note though that the latter way will allow those calls across your source code which might not be what you want.
-In this case you'll have to use source code comments.

data/docs/Feature-Envy.md

@@ -1,93 +0,0 @@
-# Feature Envy
-
-## Introduction
-
-_Feature Envy_ occurs when a code fragment references another object more often than it references itself, or when several clients do the same series of manipulations on a particular type of object.
-
-_Feature Envy_ reduces the code's ability to communicate intent: code that "belongs" on one class but which is located in another can be hard to find, and may upset the "System of Names" in the host class.
-
-_Feature Envy_ also affects the design's flexibility: A code fragment that is in the wrong class creates couplings that may not be natural within the application's domain, and creates a loss of cohesion in the unwilling host class.
-
-_Feature Envy_ often arises because it must manipulate other objects (usually its arguments) to get them into a useful form, and one force preventing them (the arguments) doing this themselves is that the common knowledge lives outside the arguments, or the arguments are of too basic a type to justify extending that type. Therefore there must be something which 'knows' about the contents or purposes of the arguments.  That thing would have to be more than just a basic type, because the basic types are either containers which don't know about their contents, or they are single objects which can't capture their relationship with their fellows of the same type. So, this thing with the extra knowledge should be reified into a class, and the utility method will most likely belong there.
-
-## Example
-
-Running Reek on:
-
-```Ruby
-class Warehouse
-  def sale_price(item)
-    (item.price - item.rebate) * @vat
-  end
-end
-```
-
-would report:
-
-```Bash
-Warehouse#sale_price refers to item more than self (FeatureEnvy)
-```
-
-since this:
-
-```Ruby
-(item.price - item.rebate)
-```
-
-belongs to the Item class, not the Warehouse.
-
-## Current Support in Reek
-
-_Feature Envy_ reports any method that refers to self less often than it refers to (ie. send messages to) some other object.
-
-## Edge cases
-
-Be aware that there are some edge cases like this code:
-
-```Ruby
-class Foo
-  def initialize
-    @map = {
-      a: ->(arg) { arg.css('table') },
-      b: ->(arg) { arg.css('div') },
-      c: ->(arg) { arg.css('span') }
-    }
-  end
-end
-```
-
-Reek cannot reliably detect that each call's receiver is a different arg and will report:
-
-```
-  [4, 5, 6]:FeatureEnvy: Foo#initialize refers to 'arg' more than self (maybe move it to another class?)
-```
-  
-If you're running into this problem you can disable this smell detector for this method either via
-configuration:
-
-```Yaml
----
-FeatureEnvy:
-  exclude:
-    - 'Foo#bar'
-```
-
-or via source code comment:
-
-```Ruby
-class Foo
-  # :reek:FeatureEnvy
-  def initialize
-    @map = {
-    # ....
-  end
-end
-```
-
-## Differences to _Utility Function_
-
-_Feature Envy_ is only triggered if there are some references to self and _[Utility Function](Utility-Function.md)_ is triggered if there are no references to self.
-
-## Configuration
-
-_Feature Envy_ supports the [Basic Smell Options](Basic-Smell-Options.md).

data/docs/How-To-Write-New-Detectors.md

@@ -1,132 +0,0 @@
-## How to write new detectors
-
-### Outline what you have in mind
-
-Before starting to code you should discuss the overall idea for your new smell detector with
-us in a corresponding github issue.
-We all should have a solid understanding of what this detector actually reports, the edgecases
-it covers and the overall rationale behind it.
-
-### Structure
-
-All smell detectors reside in `lib/reek/smell_detectors` and have the following base structure:
-
-```Ruby
-require_relative 'base_detector'
-require_relative 'smell_warning'
-
-module Reek
-  module SmellDetectors
-    #
-    # Here goes your introduction for this detector.
-    #
-    # See {file:docs/Your-Detector.md} for details.
-    class YourDetector < BaseDetector
-      def self.contexts
-        [:class] # In case you're operating on class contexts only - just an example.
-      end
-
-      #
-      # Here you should document what you expect the detector's context to look
-      # like.
-      #
-      # @return [Array<SmellWarning>]
-      #
-      def sniff
-        # "found_smells" below is just an abstraction for
-        # "find the smells in question" and iterate over them.
-        # This can just be a method but it can also be a more sophisticated set up.
-        # Check out other smell detectors to get a feeling for what to do here.
-        found_smells.map do |smell|
-          # "smell_warning" is defined in BaseDetector and should be used by you
-          # to construct smell warnings
-          smell_warning(
-            lines: [], # lines on which the smell was detected
-            message: "...", # the message that is printed on STDOUT
-            # whatever you interpolate into the "message" should go into
-            # parameters below - if you do not interpolate anything you
-            # can omit this
-            parameters: { })
-          end
-        end
-      end
-
-      private
-
-      # Here goes everything you need for finding smells.
-    end
-  end
-end
-```
-
-For your detector to be properly loaded you need to require it in `lib/reek/smell_detectors.rb` as well.
-
-### defaults.reek.yml
-
-After you ran
-
-```
-bundle exec rake
-```
-
-for the first time with your shiny new detector in place the `docs/defaults.reek.yml`
-file should have been updated automatically. Make sure you don't forget to check
-in those changes as well.
-
-### Documentation
-
-* Above every `SmellDetector::sniff` method it should be documented what the expected AST is
-* Every detector should have a separate documentation page in /docs. You can
-  take any arbitrary existing smell detector documentation page as template (since
-  they all have the same structure already)
-* The detector should be listed under [Code Smells](docs/Code-Smells.md)
-* Depending on what your detector does it might make sense to add it to other doc pages as
-  well e.g. [Simulated Polymorphism](docs/Simulated-Polymorphism.md)
-
-### Rspec examples
-
-All smell detector specs start out with 2 generic examples like below - the second one
-only if it makes sense.
-Here's what it looks like for `UncommunicativeVariableName`:
-
-```Ruby
-it 'reports the right values' do
-  src = <<-RUBY
-    def alfa
-      bravo = 5
-    end
-  RUBY
-
-  expect(src).to reek_of(:UncommunicativeVariableName,
-                         lines:   [2],
-                         context: 'alfa',
-                         message: "has the variable name 'bravo'",
-                         source:  'string',
-                         name:    'bravo')
-end
-
-it 'does count all occurences' do
-  src = <<-RUBY
-    def alfa
-      bravo = 3
-      charlie = 7
-    end
-  RUBY
-
-  expect(src).to reek_of(:UncommunicativeVariableName,
-                         lines: [2],
-                         name:  'bravo')
-  expect(src).to reek_of(:UncommunicativeVariableName,
-                         lines: [3],
-                         name:  'charlie')
-end
-```
-
-The following examples should then cover the detector specific features.
-
-### Cucumber features
-
-We are trying to write as few Cucumber features as possible.
-Normally, there should be no need to write a new feature for a new smell detector.
-If you feel like this is necessary in this case, please discuss this with us via
-github issue or in your work-in-progress pull request before doing anything.