Rename reek to Reek

troessner · Oct 17, 2015 · efdc106 · efdc106
1 parent 4384216
commit efdc106
Show file tree

Hide file tree

Showing 52 changed files with 163 additions and 163 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -66,7 +66,7 @@
 
 ## 3.0.1 (2015-07-03)
 
-* (troessner) Fix reek descending into hidden directories
+* (troessner) Fix Reek descending into hidden directories
 
 ## 3.0.0 (2015-06-30)
 
@@ -88,7 +88,7 @@
 
 ## 2.1.0 (2015-04-17)
 
-* (mvz) Ensure require 'reek' is enough to use reek's classes
+* (mvz) Ensure require 'reek' is enough to use Reek's classes
 * (mvz) Pick config file that comes first alphabetically
 * (mvz) Separate FeatureEnvy and UtilityFunction
 
@@ -137,17 +137,17 @@
 ## 1.6.0 (2014-12-27)
 
 * (troessner) Revise configuration handling:
-  Now there are 3 ways of passing reek a configuration file:
+  Now 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 (more on that later)
   - Having a file ending with .reek in your HOME directory
 
-  The order in which reek tries to find such a configuration file is exactly
-  like above: First reek checks if we have given it a configuration file
+  The order in which Reek tries to find such a configuration file is exactly
+  like above: First Reek checks if we have given it a configuration file
   explicitly via CLI. Then it checks the current working directory for a file and
   if it can't find one, it traverses up the directories until it hits the root
-  directory. And lastly, it checks your HOME directory. As soon as reek detects a
-  configuration file it stops searching immediately, meaning that from reek's
+  directory. And lastly, it checks your HOME directory. As soon as Reek detects a
+  configuration file it stops searching immediately, meaning that from Reek's
   point of view there exists one configuration file and one configuration only
   regardless of how many ".reek" files you might have on your filesystem.
 * (chastell) Add keyword arguments support after switching to 'parser'
@@ -177,7 +177,7 @@
 
 ## 1.3.7 (2014-03-25)
 
-* (gilles-leblanc) Add color to reek's output
+* (gilles-leblanc) Add color to Reek's output
 * (mvz) Ignore unused parameters if method calls super in nested context
 * (mvz) Only mark parameters uncommunicative if used
 
@@ -227,7 +227,7 @@
 
 ## 1.2.12 (2012-06-09)
 
-* (mvz) Use ripper_ruby_parser on Ruby 1.9.3 and up (thus making reek able
+* (mvz) Use ripper_ruby_parser on Ruby 1.9.3 and up (thus making Reek able
         to parse the new 1.9 hash syntax).
 
 ## 1.2.11 (2012-06-08)
@@ -446,10 +446,10 @@ See http://wiki.github.com/kevinrutherford/reek for details
 
 ### Minor enhancements
 * New smell: first naive checks for Control Couple
-* reek now only checks sources passed on the command line
+* Reek now only checks sources passed on the command line
 * Code snippets can be supplied on the commandline
 * Added headings and warnings count when smells in multiple files
-* Added Reek::RakeTask to run reek from rakefiles
+* Added Reek::RakeTask to run Reek from rakefiles
 
 ### Fixes
 * Fixed: Returns exit status 2 when smells are reported
@@ -475,7 +475,7 @@ See http://wiki.github.com/kevinrutherford/reek for details
 
 * Tweaks:
   * Now works from the source code, instead of requiring each named file
-  * Added integration tests that run reek on a couple of gems
+  * Added integration tests that run Reek on a couple of gems
 
 ## 0.2.0 2008-09-10
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
-# Contributing to reek
+# Contributing to Reek
 
-We welcome any and all contributions to reek!
+We welcome any and all contributions to Reek!
 
 If what you’re proposing requires significant work discuss it beforehand
 as an issue – it’s much easier for us to guide you towards a good
@@ -22,8 +22,8 @@ actually resolved properly or you have any additional information.
 Include the steps to reproduce the issue,
 the expected outcome and the actual outcome.
 
-Include as much information as possible: the exact reek
-invocation that you use, reek’s config and version, Ruby
+Include as much information as possible: the exact Reek
+invocation that you use, Reek’s config and version, Ruby
 version, Ruby platform (MRI, JRuby, etc.), operating system.
 
 Try to provide a minimal example that reproduces the issue.
@@ -33,7 +33,7 @@ Extra kudos if you can write it as a failing test. :)
 
 ## Setup and Pull Request Basics
 
-Fork reek, then clone it, make sure you have
+Fork Reek, then clone it, make sure you have
 [Bundler](http://bundler.io) installed, install dependencies
 and make sure all of the existing tests pass:
 
@@ -45,7 +45,7 @@ bundle
 bundle exec rake
 ```
 
-Once you’re sure your copy of reek works create your own feature branch from our "master" branch:
+Once you’re sure your copy of Reek works create your own feature branch from our "master" branch:
 
 ```
 git checkout -b your_feature_or_fix_name
@@ -84,7 +84,7 @@ Try to gauge and let us know in the pull request whether what
 you propose is a backward-compatible bugfix and should go into the
 next patch release, is a backward-compatible feature and should go
 into the next minor release, or has to break backward-compatibility
-and so needs to wait for the next major release of reek.
+and so needs to wait for the next major release of Reek.
 
 Once your PR is open someone will review it, discuss the details (if
 needed) and either merge right away or ask for some further fixes.

diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 ![reek logo](logo/reek.text.png)
 
-# `reek`: code smell detection for Ruby
+# Code smell detector for Ruby
 
 ## Overview
 
@@ -12,7 +12,7 @@
 
 ## Quickstart
 
-`reek` is a tool that examines Ruby classes, modules and methods and reports any
+Reek is a tool that examines Ruby classes, modules and methods and reports any
 [Code Smells](docs/Code-Smells.md) it finds.
 Install it like this:
 
@@ -41,7 +41,7 @@ class Dirty
 end
 ```
 
-`reek` will report the following code smells in this file:
+Reek will report the following code smells in this file:
 
 ```
 $ reek demo.rb
@@ -58,7 +58,7 @@ demo.rb -- 8 warnings:
 
 ## Fixing Smell Warnings
 
-`reek` focuses on high-level code smells, so we can't tell you how to fix warnings in
+Reek focuses on high-level code smells, so we can't tell you how to fix warnings in
 a generic fashion; this is and will always be completely dependent on your domain
 language and bussiness logic.
 
@@ -154,7 +154,7 @@ $stdin -- 3 warnings:
 
 ## Code smells
 
-`reek` currently includes checks for some aspects of
+Reek currently includes checks for some aspects of
 [Control Couple](docs/Control-Couple.md),
 [Data Clump](docs/Data-Clump.md),
 [Feature Envy](docs/Feature-Envy.md),
@@ -165,7 +165,7 @@ $stdin -- 3 warnings:
 [Uncommunicative Name](docs/Uncommunicative-Name.md),
 [Unused Parameters](docs/Unused-Parameters.md)
 and more. See the [Code Smells](docs/Code-Smells.md)
-for up to date details of exactly what `reek` will check in your code.
+for up to date details of exactly what Reek will check in your code.
 
 ## Configuration
 
@@ -183,29 +183,29 @@ For a summary of those CLI options see [Command-Line Options](docs/Command-Line-
 
 #### Configuration loading
 
-Configuring `reek` via a configuration file is by far the most powerful way.
+Configuring Reek via a configuration file is by far the most powerful way.
 
 There are three ways of passing `reek` a configuration file:
 
 1. Using the CLI `-c` switch (see [_Command-line interface_](#command-line-interface) above)
 2. Having a file ending with `.reek` either in your current working directory or in a parent directory (more on that later)
 3. Having a file ending with `.reek` in your home directory
 
-The order in which `reek` tries to find such a configuration
+The order in which Reek tries to find such a configuration
 file is exactly the above: first it checks if we have given
 it a configuration file explicitly via CLI; then it checks
 the current working directory for a file and if it can't
 find one, it traverses up the directories until it hits the
 root directory; lastly, it checks your home directory.
 
-As soon as `reek` detects a configuration file it stops searching
-immediately, meaning that from `reek`'s point of view there exists
+As soon as Reek detects a configuration file it stops searching
+immediately, meaning that from Reek's point of view there exists
 exactly one configuration file and one configuration, regardless
 of how many `*.reek` files you might have on your filesystem.
 
 #### Configuration options
 
-We put a lot of effort into making `reek`'s configuration as self explanatory as possible so the
+We put a lot of effort into making Reek's configuration as self explanatory as possible so the
 best way to understand it is by looking at a simple
 example (e.g. `config.reek` in your project directory):
 
@@ -218,8 +218,8 @@ example (e.g. `config.reek` in your project directory):
 IrresponsibleModule:
   enabled: false
 
-# You can use filters to silence reek warnings.
-# Either because you simply disagree with reek (we are not the police) or
+# You can use filters to silence Reek warnings.
+# Either because you simply disagree with Reek (we are not the police) or
 # because you want to fix this at a later point in time.
 NestedIterators:
   exclude:
@@ -295,13 +295,13 @@ Besides the obvious
 reek [options] [dir_or_source_file]*
 ```
 
-there are quite a few other ways how to use `reek` in your projects:
+there are quite a few other ways how to use Reek in your projects:
 
-* Use `reek`'s [Rake task](docs/Rake-Task.md) to automate detecting code smells
-* Add `reek`'s custom matcher to your [RSpec examples](docs/RSpec-matchers.md)
-* Include `reek` using the [Developer API](docs/API.md)
+* Use Reek's [Rake task](docs/Rake-Task.md) to automate detecting code smells
+* Add Reek's custom matcher to your [RSpec examples](docs/RSpec-matchers.md)
+* Include Reek using the [Developer API](docs/API.md)
 
-## Developing `reek` / Contributing
+## Developing Reek / Contributing
 
 The first thing you want to do after checking out the source code is to run Bundler:
 
@@ -325,7 +325,7 @@ bundle exec rake
 ```
 
 From then on you should check out:
-* [How reek works internally](docs/How-reek-works-internally.md)
+* [How Reek works internally](docs/How-reek-works-internally.md)
 * [the contributing guide](CONTRIBUTING.md)
 
 
@@ -346,7 +346,7 @@ If you don't feel like getting your hands dirty with code there are still other
 
 ## Working with Rails
 
-Making `reek` "Rails"-friendly is fairly simple since we support directory specific configurations (`directory directives` in `reek` talk).
+Making Reek "Rails"-friendly is fairly simple since we support directory specific configurations (`directory directives` in Reek talk).
 Just add this to your configuration file:
 
 ```Yaml
@@ -362,7 +362,7 @@ Just add this to your configuration file:
     enabled: false
 ```
 
-Be careful though, `reek` does not merge your configuration entries, so if you already have a directory directive for "app/controllers" or "app/helpers" you need to update those directives instead of copying the above YAML sample into your configuration file.
+Be careful though, Reek does not merge your configuration entries, so if you already have a directory directive for "app/controllers" or "app/helpers" you need to update those directives instead of copying the above YAML sample into your configuration file.
 
 ## Integrations
 
@@ -375,9 +375,9 @@ Be careful though, `reek` does not merge your configuration entries, so if you a
 ### Projects that use or support us
 
 * [overcommit](https://github.com/brigade/overcommit) - a Git commit hook manager with support for
-  `reek`
+  Reek
 * [ruby-critic](https://github.com/whitesmith/rubycritic) - gem that wraps around static analysis gems such as `reek`, [flay](https://github.com/seattlerb/flay) and [flog](https://github.com/seattlerb/flog)
-* [pronto-reek](https://github.com/mmozuras/pronto-reek) - `reek` integration for [pronto](https://github.com/mmozuras/pronto)
+* [pronto-reek](https://github.com/mmozuras/pronto-reek) - Reek integration for [pronto](https://github.com/mmozuras/pronto)
 
 ### Misc
 
@@ -398,13 +398,13 @@ report
 
 ## Contributors
 
-The `reek` core team consists of:
+The Reek core team consists of:
 
 * [Matijs van Zuijlen](https://github.com/mvz)
 * [Piotr Szotkowski](https://github.com/chastell)
 * [Timo Rößner](https://github.com/troessner)
 
-The original author of `reek` is [Kevin Rutherford](https://github.com/kevinrutherford).
+The original author of Reek is [Kevin Rutherford](https://github.com/kevinrutherford).
 
 The author of Reek’s logo is [Sonja Heinen](http://yippee.io).
 

diff --git a/docs/API.md b/docs/API.md
@@ -1,4 +1,4 @@
-# Using `reek` inside your Ruby application
+# Using Reek inside your Ruby application
 
 ## Installation
 
@@ -52,7 +52,7 @@ Note that `Reek::Examiner.new` can take `source` as `String`, `Pathname`, `File`
 
 ## Choosing your output format
 
-Besides normal text output, `reek` can generate output in YAML,
+Besides normal text output, Reek can generate output in YAML,
 JSON, HTML and XML by using the following Report types:
 
 ```

diff --git a/docs/Attribute.md b/docs/Attribute.md
@@ -18,7 +18,7 @@ class Klass
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
 reek test.rb

diff --git a/docs/Boolean-Parameter.md b/docs/Boolean-Parameter.md
@@ -24,7 +24,7 @@ class Dummy
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
 test.rb -- 3 warnings:

diff --git a/docs/Class-Variable.md b/docs/Class-Variable.md
@@ -16,10 +16,10 @@ class Dummy
 end
 ```
 
-`reek` would emit the following warning:
+Reek would emit the following warning:
 
 ```
-reek test.rb 
+reek test.rb
 
 test.rb -- 1 warning:
   [2]:Dummy declares the class variable @@class_variable (ClassVariable)

diff --git a/docs/Command-Line-Options.md b/docs/Command-Line-Options.md
@@ -2,7 +2,7 @@
 
 ## Introduction
 
-reek follows standard Unix convention for passing arguments.
+`reek` follows standard Unix convention for passing arguments.
 
 Check out
 
@@ -74,7 +74,7 @@ This mode can be enabled via the "-U" or "--ultra-verbose" flag.
 So for instance, if your test file would smell of _ClassVariable_, this is what the _reek_ output would look like:
 
 ```Bash
-reek -U test.rb 
+reek -U test.rb
 ```
 ```
 test.rb -- 1 warning:

diff --git a/docs/Control-Couple.md b/docs/Control-Couple.md
@@ -10,13 +10,13 @@ Control Coupling reduces the code's flexibility by creating a dependency between
 
 You can find a good write-up regarding this problem [here](http://solnic.eu/2012/04/11/get-rid-of-that-code-smell-control-couple.html).
 
-## Current Support in reek
+## Current Support in Reek
 
-`reek` warns about control coupling when:
+Reek warns about control coupling when:
 
 * [Control-Parameter](Control-Parameter.md) - a method parameter or block parameter is the tested value in a conditional statement (as in the example below); or
 * [Boolean-Parameter](Boolean-Parameter.md) - a method parameter is defaulted to `true` or `false`.
 
 ## Configuration
 
-Control Couple supports the [Basic Smell Options](Basic-Smell-Options.md).
+Control Couple supports the [Basic Smell Options](Basic-Smell-Options.md).
diff --git a/docs/Control-Parameter.md b/docs/Control-Parameter.md
@@ -20,9 +20,9 @@ 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 "write_quoted" / "write_unquoted" in the initial caller of "write".
 
-## Current Support in reek
+## Current Support in Reek
 
-`reek` warns about control coupling when a method parameter or block parameter is the tested value in a conditional statement.
+Reek warns about control coupling when a method parameter or block parameter is the tested value in a conditional statement.
 
 ## Configuration
-Original file line number
+Diff line change
@@ Expand Up / @@ -18,7 +18,7 @@ class Klass @@
     end
     ```
-    `reek` would emit the following warning:
+    Reek would emit the following warning:
     ```
     reek test.rb
@@ Expand Down @@