reek 3.5.0 → 3.6.0

data/docs/Too-Many-Instance-Variables.md

@@ -24,19 +24,19 @@ class TooManyInstanceVariables
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
 test.rb -- 5 warnings:
   [1]:TooManyInstanceVariables has at least 4 instance variables (TooManyInstanceVariables)
 ```
-## Current Support in `reek`
+## Current Support in Reek
 
-`reek` only counts the instance variables you use explicitly like in the example above. Class macros like `attr_accessor` are disregarded.
+Reek only counts the instance variables you use explicitly like in the example above. Class macros like `attr_accessor` are disregarded.
 
 ## Configuration
 
-`reek`'s `Too Many Instance Variables` detector offers the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's `Too Many Instance Variables` detector offers the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|

data/docs/Too-Many-Methods.md

@@ -22,15 +22,15 @@ class TooManyMethods
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
 test.rb -- 1 warning:
   [1]:TooManyMethods has at least 4 methods (TooManyMethods)
 ```
-## Current Support in `reek`
+## Current Support in Reek
 
-`reek` counts all the methods it can find in a `class` - instance *and* class methods. So given `max_methods` from above is 4, this:
+Reek counts all the methods it can find in a `class` - instance *and* class methods. So given `max_methods` from above is 4, this:
 
 ```Ruby
 class TooManyMethods
@@ -44,11 +44,11 @@ class TooManyMethods
 end
 ```
 
-would cause reek to emit the same warning as in the example above.
+would cause Reek to emit the same warning as in the example above.
 
 ## Configuration
 
-`reek`'s `Too Many Methods` detector offers the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's `Too Many Methods` detector offers the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|

data/docs/Too-Many-Statements.md

@@ -6,7 +6,7 @@ A method with `Too Many Statements` is any method that has a large number of lin
 
 ## Current Support in Reek
 
-`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.
+`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:
 
@@ -30,7 +30,7 @@ end
 
 ## Configuration
 
-`reek`'s `Too Many Statements` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's `Too Many Statements` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|

data/docs/Uncommunicative-Method-Name.md

@@ -6,7 +6,7 @@ An `Uncommunicative Method Name` is a method name that doesn't communicate its i
 
 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.
 
-## Current Support in reek
+## Current Support in Reek
 
 `Uncommunicative Method Name` checks for:
 
@@ -16,9 +16,9 @@ Poor names make it hard for the reader to build a mental picture of what's going
 
 ## Configuration
 
-`reek`'s Uncommunicative Method Name detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's Uncommunicative Method Name detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|
-| `reject` | array of regular expressions | The set of regular expressions that `reek` uses to check for bad names. Defaults to `[/^[a-z]$/, /[0-9]$/, /[A-Z]/]`. |
-| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. |
+| `reject` | array of regular expressions | The set of regular expressions that Reek uses to check for bad names. Defaults to `[/^[a-z]$/, /[0-9]$/, /[A-Z]/]`. |
+| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. |

data/docs/Uncommunicative-Module-Name.md

@@ -6,7 +6,7 @@ An `Uncommunicative Module Name` is a module name that doesn't communicate its i
 
 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.
 
-## Current Support in reek
+## Current Support in Reek
 
 `Uncommunicative Module Name` checks for:
 
@@ -15,9 +15,9 @@ Poor names make it hard for the reader to build a mental picture of what's going
 
 ## Configuration
 
-`reek`'s `Uncommunicative Module Name` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's `Uncommunicative Module Name` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|
-| `reject` | array of regular expressions | The set of regular expressions that `reek` uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/]`. |
-| `accept` | array of names as strings | List of names that will be accepted (not reported) even if they match one of the `reject` expressions. Empty by default.|
+| `reject` | array of regular expressions | The set of regular expressions that Reek uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/]`. |
+| `accept` | array of names as strings | List of names that will be accepted (not reported) even if they match one of the `reject` expressions. Empty by default.|

data/docs/Uncommunicative-Name.md

@@ -8,9 +8,9 @@ Poor names make it hard for the reader to build a mental picture of what's going
 
 ## Current Support in Reek
 
-`reek` offers four related checks:
+Reek offers four related checks:
 
 * [Uncommunicative Method Name](Uncommunicative-Method-Name.md)
 * [Uncommunicative Module Name](Uncommunicative-Module-Name.md)
 * [Uncommunicative Parameter Name](Uncommunicative-Parameter-Name.md)
-* [Uncommunicative Variable Name](Uncommunicative-Variable-Name.md)
+* [Uncommunicative Variable Name](Uncommunicative-Variable-Name.md)

data/docs/Uncommunicative-Parameter-Name.md

@@ -6,7 +6,7 @@ An `Uncommunicative Parameter Name` is a parameter name that doesn't communicate
 
 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.
 
-## Current Support in reek
+## Current Support in Reek
 
 `Uncommunicative Parameter Name` checks for:
 
@@ -16,9 +16,9 @@ Poor names make it hard for the reader to build a mental picture of what's going
 
 ## Configuration
 
-`reek`'s Uncommunicative Parameter Name detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's Uncommunicative Parameter Name detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|
-| `reject` | array of regular expressions | The set of regular expressions that `reek` uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/, /[A-Z]/]@. |
-| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. |
+| `reject` | array of regular expressions | The set of regular expressions that Reek uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/, /[A-Z]/]@. |
+| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. |

data/docs/Uncommunicative-Variable-Name.md

@@ -16,9 +16,9 @@ Poor names make it hard for the reader to build a mental picture of what's going
 
 ## Configuration
 
-`reek`'s `Uncommunicative Variable Name` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's `Uncommunicative Variable Name` detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|
-| `reject` | array of regular expressions | The set of regular expressions that `reek` uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/, /[A-Z]/]`. |
-| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. Defaults to @['_']@.|
+| `reject` | array of regular expressions | The set of regular expressions that Reek uses to check for bad names. Defaults to `[/^.$/, /[0-9]$/, /[A-Z]/]`. |
+| `accept` | array of strings or regular expressions | Name that will be accepted (not reported) even if they match one of the `reject` expressions. Defaults to @['_']@.|

data/docs/Unused-Parameters.md

@@ -16,7 +16,7 @@ class Klass
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
 [2]:Klass#unused_parameters has unused parameter 'z' (UnusedParameters)
@@ -24,4 +24,4 @@ end
 
 ## Configuration
 
-`Unused Parameter` offers the [Basic Smell Options](Basic-Smell-Options.md).
+`Unused Parameter` offers the [Basic Smell Options](Basic-Smell-Options.md).

data/docs/Utility-Function.md

@@ -18,14 +18,14 @@ class UtilityFunction
 end
 ```
 
-`reek` would report:
+Reek would report:
 
 ```
 test.rb -- 2 warnings:
   [2]:UtilityFunction#showcase doesn't depend on instance state (UtilityFunction)
 ```
 
-## Current Support in reek
+## Current Support in Reek
 
 _Utility Function_ will warn about any method that:
 
@@ -41,7 +41,7 @@ _[Feature Envy](Feature-Envy.md)_ is only triggered if there are some references
 
 ## Configuration
 
-`reek`'s _Utility Function_ detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
+Reek's _Utility Function_ detector supports the [Basic Smell Options](Basic-Smell-Options.md), plus:
 
 | Option         | Value       | Effect  |
 | ---------------|-------------|---------|
@@ -53,4 +53,4 @@ A sample configuration file would look like this:
 ---
 UtilityFunction:
   public_methods_only: true
-``
+```

data/docs/Versioning-Policy.md

@@ -1,7 +1,7 @@
 # Versioning Policy
 
-* CLI interface: Adding options is a non-breaking change, and would warrant an update of the minor version. Removing options is a breaking change and requires a major version update (we did this going to reek 2). Adding a report format probably also warrents a minor version upgrade.
-* API: We haven't really defined a 'public' API for using Reek programmatically, and we've only just started testing it. So, this is basically a blank slate at the moment. We will work on this as a part of the reek 3 release.
+* CLI interface: Adding options is a non-breaking change, and would warrant an update of the minor version. Removing options is a breaking change and requires a major version update (we did this going to Reek 2). Adding a report format probably also warrents a minor version upgrade.
+* API: We haven't really defined a 'public' API for using Reek programmatically, and we've only just started testing it. So, this is basically a blank slate at the moment. We will work on this as a part of the Reek 3 release.
 * List of detected smells: Adding a smell warrants a minor release, removing a smell is a breaking change. This makes sense if you consider that the CLI allows running a single smell detector.
 * Consistency of detected smells: This is very hard to guarantee. If we fix a bug in one of the detectors, some fragrant code may become smelly, or vice versa. Right now we don't bother with this.
 * Smell configuration: The detectors are quite tolerant regarding configuration options that they don't recognize, so we regard any change here as only requiring a minor release.

data/features/command_line_interface/options.feature

@@ -1,5 +1,5 @@
 Feature: Reek can be controlled using command-line options
-  In order to change reek's default behaviour
+  In order to change Reek's default behaviour
   As a developer
   I want to supply options on the command line
 

data/features/configuration_files/directory_specific_directives.feature

@@ -1,8 +1,8 @@
 Feature: Directory directives
-  In order to have a more fine-grained control over what reek reports
+  In order to have a more fine-grained control over what Reek reports
   And to enable domain specific modes (like a Ruby on Rails mode)
   As a user
-  I want to be able to configure reek using directory directives
+  I want to be able to configure Reek using directory directives
 
   Scenario: Configure multiple directories
     Given a file named "web_app/config.reek" with:
@@ -206,8 +206,8 @@ Feature: Directory directives
     And stderr reports:
     """
     You are trying to configure smell type IteratorsNested but we can't find one with that name.
-    Please make sure you spelled it right (see 'config/defaults.reek' in the reek
-    repository for a list of all available smell types.
+    Please make sure you spelled it right. (See 'defaults.reek' in the Reek
+    repository for a list of all available smell types.)
 
     """
 

data/features/configuration_loading.feature

@@ -1,16 +1,16 @@
 Feature: Offer different ways how to load configuration
 
-  There are 3 ways of passing reek a configuration file:
-  - Using the cli "-c" switch
-  - Having a file ending with .reek either in your current working directory or in a parent directory
-  - Having a file ending with .reek in your HOME directory
-  The order in which reek tries to find such a configuration file should exactly be like above:
-  First reek should check if we have given it a configuration file explicitly via CLI.
-  Then it should check the current working directory for a file and if it can't find one,
-  it should traverse up the directories until it hits the root directory.
-  And finally, it should check your HOME directory.
+  Reek can be configured in two ways:
+  - Using the cli "-c" switch to pass a configuration file on the command line.
+  - Having a Reek configuration file that is automatically found. Reek will
+    look for a file ending in .reek in the following places, in order:
+    - The current working directory
+    - The working directory's ancestor directories, traversing all the way up
+      to the root.
+    - Your HOME directory
+    Reek will check these in order and stop after the first file found.
 
-  Scenario: No configuration
+  Scenario: Default configuration
     Given a smelly file called 'smelly.rb'
     When I run reek smelly.rb
     Then the exit status indicates smells
@@ -36,20 +36,6 @@ Feature: Offer different ways how to load configuration
     Then it reports no errors
     And it succeeds
 
-  Scenario: Configuration file in the parent directory of the working directory
-    Given a smelly file called 'smelly.rb' in a subdirectory
-    And a masking configuration file called 'config.reek'
-    When I run "reek smelly.rb" in the subdirectory
-    Then it reports no errors
-    And it succeeds
-
-  Scenario: Configuration file in the HOME directory
-    Given a smelly file called 'smelly.rb'
-    And a masking configuration file in the HOME directory
-    When I run reek smelly.rb
-    Then it reports no errors
-    And it succeeds
-
   Scenario: Two opposing configuration files and we stop after the first one
     Given a smelly file called 'smelly.rb' in a subdirectory
     And an enabling configuration file in the subdirectory

data/features/programmatic_access.feature

@@ -1,5 +1,5 @@
-Feature: Using reek programmatically
-  In order to use reek from inside my program
+Feature: Using Reek programmatically
+  In order to use Reek from inside my program
   As a developer
   I want to be able to use its classes
 
@@ -22,7 +22,7 @@ Feature: Using reek programmatically
       has the name 'm'
       """
 
-  Scenario: Using reek's built-in report classes
+  Scenario: Using Reek's built-in report classes
     Given a smelly file called 'smelly.rb'
     And a file named "examine.rb" with:
       """

data/features/reports/json.feature

@@ -1,5 +1,5 @@
 Feature: Report smells using simple JSON layout
-  In order to parse reek's output simply and consistently, simply
+  In order to parse Reek's output simply and consistently, simply
   output a list of smells in JSON.
 
   Scenario: output is empty when there are no smells

data/features/reports/reports.feature

@@ -1,7 +1,7 @@
 Feature: Correctly formatted reports
-  In order to get the most out of reek
+  In order to get the most out of Reek
   As a developer
-  I want to be able to parse reek's output simply and consistently
+  I want to be able to parse Reek's output simply and consistently
 
   Scenario Outline: two reports run together with indented smells
     Given a directory called 'smelly' containing two smelly files

data/features/reports/yaml.feature

@@ -1,5 +1,5 @@
 Feature: Report smells using simple YAML layout
-  In order to parse reek's output simply and consistently, simply
+  In order to parse Reek's output simply and consistently, simply
   output a list of smells in Yaml.
 
   Scenario: output is empty when there are no smells

data/lib/reek/ast/sexp_extensions.rb

@@ -1,500 +1,19 @@
 require_relative 'reference_collector'
 
-module Reek
-  module AST
-    #
-    # Extension modules providing utility methods to ASTNode objects, depending
-    # on their type.
-    #
-    module SexpExtensions
-      # Base module for utility methods for argument nodes.
-      module ArgNodeBase
-        def name
-          children.first
-        end
-
-        # Other is a symbol?
-        def ==(other)
-          name == other
-        end
-
-        def marked_unused?
-          plain_name.start_with?('_')
-        end
-
-        def plain_name
-          name.to_s
-        end
-
-        def block?
-          false
-        end
-
-        def optional_argument?
-          false
-        end
-
-        def anonymous_splat?
-          false
-        end
-
-        def components
-          [self]
-        end
-      end
-
-      # Utility methods for :arg nodes.
-      module ArgNode
-        include ArgNodeBase
-      end
-
-      # Utility methods for :kwarg nodes.
-      module KwargNode
-        include ArgNodeBase
-      end
-
-      # Utility methods for :optarg nodes.
-      module OptargNode
-        include ArgNodeBase
-
-        def optional_argument?
-          true
-        end
-      end
-
-      # Utility methods for :kwoptarg nodes.
-      module KwoptargNode
-        include ArgNodeBase
-
-        def optional_argument?
-          true
-        end
-      end
-
-      # Utility methods for :blockarg nodes.
-      module BlockargNode
-        include ArgNodeBase
-        def block?
-          true
-        end
-      end
-
-      # Utility methods for :restarg nodes.
-      module RestargNode
-        include ArgNodeBase
-        def anonymous_splat?
-          !name
-        end
-      end
-
-      # Utility methods for :kwrestarg nodes.
-      module KwrestargNode
-        include ArgNodeBase
-        def anonymous_splat?
-          !name
-        end
-      end
-
-      # Utility methods for :shadowarg nodes.
-      module ShadowargNode
-        include ArgNodeBase
-      end
-
-      # Base module for utility methods for nodes that can contain argument
-      # nodes nested through :mlhs nodes.
-      module NestedAssignables
-        def components
-          children.flat_map(&:components)
-        end
-      end
-
-      # Utility methods for :args nodes.
-      module ArgsNode
-        include NestedAssignables
-      end
-
-      # Utility methods for :mlhs nodes.
-      module MlhsNode
-        include NestedAssignables
-      end
-
-      # Base module for utility methods for :and and :or nodes.
-      module LogicOperatorBase
-        def condition() children.first end
-
-        def body_nodes(type, ignoring = [])
-          children[1].find_nodes type, ignoring
-        end
-      end
-
-      # Utility methods for :and nodes.
-      module AndNode
-        include LogicOperatorBase
-      end
-
-      # Utility methods for :or nodes.
-      module OrNode
-        include LogicOperatorBase
-      end
-
-      # Utility methods for :attrasgn nodes.
-      module AttrasgnNode
-        def args() children[2] end
-      end
-
-      # Utility methods for :case nodes.
-      module CaseNode
-        def condition() children.first end
-
-        def body_nodes(type, ignoring = [])
-          children[1..-1].compact.flat_map { |child| child.find_nodes(type, ignoring) }
-        end
-
-        def else_body
-          children.last
-        end
-      end
-
-      # Utility methods for :when nodes.
-      module WhenNode
-        def condition_list
-          children[0..-2]
-        end
-
-        def body
-          children.last
-        end
-      end
-
-      # Utility methods for :send nodes.
-      module SendNode
-        def receiver; children.first; end
-        def method_name() children[1]; end
-        def args() children[2..-1] end
-
-        def participants
-          ([receiver] + args).compact
-        end
-
-        def arg_names
-          args.map { |arg| arg.children.first }
-        end
-
-        def module_creation_call?
-          object_creation_call? && module_creation_receiver?
-        end
-
-        def module_creation_receiver?
-          receiver && [:Class, :Struct].include?(receiver.simple_name)
-        end
-
-        def object_creation_call?
-          method_name == :new
-        end
-
-        def visibility_modifier?
-          VISIBILITY_MODIFIERS.include?(method_name)
-        end
-
-        def attribute_writer?
-          ATTR_DEFN_METHODS.include?(method_name) ||
-            attr_with_writable_flag?
-        end
-
-        # Handles the case where we create an attribute writer via:
-        # attr :foo, true
-        def attr_with_writable_flag?
-          method_name == :attr && args.any? && args.last.type == :true
-        end
-
-        VISIBILITY_MODIFIERS = [:private, :public, :protected, :module_function]
-        ATTR_DEFN_METHODS = [:attr_writer, :attr_accessor]
-      end
-
-      Op_AsgnNode = SendNode
-
-      # Base module for utility methods for nodes representing variables.
-      module VariableBase
-        def name() children.first end
-      end
-
-      # Utility methods for :cvar nodes.
-      module CvarNode
-        include VariableBase
-      end
-
-      CvasgnNode = CvarNode
-      CvdeclNode = CvarNode
-
-      # Utility methods for :ivar nodes.
-      module IvarNode
-        include VariableBase
-      end
-
-      # Utility methods for :ivasgn nodes.
-      module IvasgnNode
-        include VariableBase
-      end
-
-      # Utility methods for :lvar nodes.
-      module LvarNode
-        include VariableBase
-
-        alias_method :simple_name, :name
-        alias_method :var_name,    :name
-      end
-
-      LvasgnNode = LvarNode
-
-      # Base module for utility methods for :def and :defs nodes.
-      module MethodNodeBase
-        def arguments
-          parameters.reject(&:block?)
-        end
-
-        def arg_names
-          arguments.map(&:name)
-        end
-
-        def parameters
-          argslist.components
-        end
-
-        def parameter_names
-          parameters.map(&:name)
-        end
-
-        def name_without_bang
-          name.to_s.chop
-        end
-
-        def ends_with_bang?
-          name[-1] == '!'
-        end
-
-        def body_nodes(types, ignoring = [])
-          if body
-            body.find_nodes(types, ignoring)
-          else
-            []
-          end
-        end
-      end
-
-      # Checking if a method is a singleton method.
-      module SingletonMethod
-        def singleton_method?
-          singleton_method_via_class_self_notation?
-        end
-
-        # Ruby allows us to make a method a singleton_method using the
-        # class << self syntax.
-        #
-        # To check for this we check if the parent node is of type :sclass.
-        #
-        # @return [Boolean]
-        def singleton_method_via_class_self_notation?
-          return unless parent
-          parent.type == :sclass
-        end
-      end
-
-      # Utility methods for :def nodes.
-      module DefNode
-        def name() children.first end
-        def argslist() children[1] end
-
-        def body
-          children[2]
-        end
-
-        def full_name(outer)
-          prefix = outer == '' ? '' : "#{outer}#"
-          "#{prefix}#{name}"
-        end
-
-        def depends_on_instance?
-          ReferenceCollector.new(self).num_refs_to_self > 0
-        end
-
-        include MethodNodeBase
-        include SingletonMethod
-      end
-
-      # Utility methods for :defs nodes.
-      module DefsNode
-        def receiver() children.first end
-        def name() children[1] end
-        def argslist() children[2] end
-
-        def body
-          children[3]
-        end
-
-        include MethodNodeBase
-
-        def full_name(outer)
-          prefix = outer == '' ? '' : "#{outer}#"
-          "#{prefix}#{SexpFormatter.format(receiver)}.#{name}"
-        end
-
-        def depends_on_instance?
-          false
-        end
-      end
-
-      # Utility methods for :if nodes.
-      module IfNode
-        def condition() children.first end
-
-        def body_nodes(type, ignoring = [])
-          children[1..-1].compact.flat_map { |child| child.find_nodes(type, ignoring) }
-        end
-      end
-
-      # Utility methods for :block nodes.
-      module BlockNode
-        def call() children.first end
-        def args() children[1] end
-        def block() children[2] end
-        def parameters() children[1] || [] end
-
-        def parameter_names
-          parameters.children
-        end
-
-        def simple_name
-          :block
-        end
-
-        def without_block_arguments?
-          args.components.empty?
-        end
-      end
-
-      # Utility methods for :lit nodes.
-      module LitNode
-        def value() children.first end
-      end
-
-      # Utility methods for :const nodes.
-      module ConstNode
-        def simple_name
-          children.last
-        end
-      end
-
-      # Base module for utility methods for module nodes.
-      module ModuleNodeBase
-        # The full name of the module or class, including the name of any
-        # module or class it is nested inside of.
-        #
-        # For example, given code like this:
-        #
-        #   module Foo
-        #     class Bar::Baz
-        #     end
-        #   end
-        #
-        # The full name for the inner class will be 'Foo::Bar::Baz'. To return
-        # the correct name, the name of the outer context has to be passed into this method.
-        #
-        # @param outer [String] full name of the wrapping module or class
-        # @return the module's full name
-        def full_name(outer)
-          prefix = outer == '' ? '' : "#{outer}::"
-          "#{prefix}#{name}"
-        end
-
-        # The final section of the module or class name. For example, for a
-        # module with name 'Foo::Bar' this will return 'Bar'; for a module with
-        # name 'Foo' this will return 'Foo'.
-        #
-        # @return [String] the final section of the name
-        def simple_name
-          name.split('::').last
-        end
-      end
-
-      # Utility methods for :module nodes.
-      module ModuleNode
-        include ModuleNodeBase
-
-        # @return [String] name as given in the module statement
-        def name
-          SexpFormatter.format(children.first)
-        end
-      end
-
-      # Utility methods for :class nodes.
-      module ClassNode
-        include ModuleNode
-        def superclass() children[1] end
-      end
-
-      # Utility methods for :casgn nodes.
-      module CasgnNode
-        include ModuleNodeBase
-
-        def defines_module?
-          return false unless value
-          call = case value.type
-                 when :block
-                   value.call
-                 when :send
-                   value
-                 end
-          call && call.module_creation_call?
-        end
-
-        def name
-          SexpFormatter.format(children[1])
-        end
-
-        # there are two valid forms of the casgn sexp
-        # (casgn <namespace> <name> <value>) and
-        # (casgn <namespace> <name>) used in or-asgn and mlhs
-        #
-        # source = "class Hi; THIS ||= 3; end"
-        # (class
-        #   (const nil :Hi) nil
-        #   (or-asgn
-        #    (casgn nil :THIS)
-        #    (int 3)))
-        def value
-          children[2]
-        end
-      end
-
-      # Utility methods for :yield nodes.
-      module YieldNode
-        def args() children end
-
-        def arg_names
-          args.map { |arg| arg[1] }
-        end
-      end
-
-      # Utility methods for :super nodes.
-      module SuperNode
-        def method_name
-          :super
-        end
-      end
-
-      ZsuperNode = SuperNode
-
-      # Utility methods for :sym nodes.
-      module SymNode
-        def name
-          children.first
-        end
-
-        def full_name(outer)
-          prefix = outer == '' ? '' : "#{outer}#"
-          "#{prefix}#{name}"
-        end
-      end
-    end
-  end
-end
+require_relative 'sexp_extensions/arguments'
+require_relative 'sexp_extensions/attribute_assignments'
+require_relative 'sexp_extensions/block'
+require_relative 'sexp_extensions/case'
+require_relative 'sexp_extensions/constant'
+require_relative 'sexp_extensions/if'
+require_relative 'sexp_extensions/literal'
+require_relative 'sexp_extensions/logical_operators'
+require_relative 'sexp_extensions/methods'
+require_relative 'sexp_extensions/module'
+require_relative 'sexp_extensions/nested_assignables'
+require_relative 'sexp_extensions/send'
+require_relative 'sexp_extensions/super'
+require_relative 'sexp_extensions/symbols'
+require_relative 'sexp_extensions/variables'
+require_relative 'sexp_extensions/when'
+require_relative 'sexp_extensions/yield'