rubycritic 3.4.0 → 3.5.0

data/.todo.reek

@@ -1,142 +0,0 @@
----
-IrresponsibleModule:
-  exclude:
-  - RubyCritic::Analyser::Attributes
-  - RubyCritic::Analyser::Churn
-  - RubyCritic::Analyser::Complexity
-  - Parser::AST::Node
-  - RubyCritic::AST::EmptyNode
-  - RubyCritic::Flay
-  - RubyCritic::Flog
-  - RubyCritic::MethodsCounter
-  - RubyCritic::ModulesLocator
-  - RubyCritic::Parser
-  - RubyCritic::Reek
-  - RubyCritic::Analyser::FlaySmells
-  - RubyCritic::Analyser::FlogSmells
-  - RubyCritic::Analyser::ReekSmells
-  - RubyCritic::AnalysersRunner
-  - RubyCritic::Browser
-  - RubyCritic::Cli::Application
-  - RubyCritic::Cli::Options
-  - RubyCritic::Colorize
-  - RubyCritic::CommandFactory
-  - RubyCritic::Command::Base
-  - RubyCritic::Command::Ci
-  - RubyCritic::Command::Default
-  - RubyCritic::Command::Help
-  - RubyCritic::Command::StatusReporter
-  - RubyCritic::Command::Version
-  - RubyCritic::Config
-  - RubyCritic::Configuration
-  - RubyCritic::AnalysedModule
-  - RubyCritic::AnalysedModulesCollection
-  - RubyCritic::Location
-  - RubyCritic::Rating
-  - RubyCritic::Smell
-  - RubyCritic::Generator::ConsoleReport
-  - RubyCritic::Generator::Html::Base
-  - RubyCritic::Generator::Html::CodeFile
-  - RubyCritic::Generator::Html::CodeIndex
-  - RubyCritic::Generator::Html::Line
-  - RubyCritic::Generator::Html::Overview
-  - RubyCritic::Generator::Html::SmellsIndex
-  - RubyCritic::Turbulence
-  - RubyCritic::ViewHelpers
-  - RubyCritic::Generator::HtmlReport
-  - RubyCritic::Generator::Json::Simple
-  - RubyCritic::Generator::JsonReport
-  - RubyCritic::Generator::Text::List
-  - RubyCritic::Reporter
-  - RubyCritic::RevisionComparator
-  - RubyCritic::Serializer
-  - RubyCritic::SmellsStatusSetter
-  - RubyCritic::SourceControlSystem::Base
-  - RubyCritic::SourceControlSystem::Double
-  - RubyCritic::SourceControlSystem::Git
-  - RubyCritic::SourceControlSystem::Mercurial
-  - RubyCritic::SourceLocator
-  - RubyCritic
-Attribute:
-  exclude:
-  - RubyCritic::Analyser::Churn#source_control_system
-  - RubyCritic::Configuration#deduplicate_symlinks
-  - RubyCritic::Configuration#format
-  - RubyCritic::Configuration#mode
-  - RubyCritic::Configuration#no_browser
-  - RubyCritic::Configuration#open_with
-  - RubyCritic::Configuration#source_control_system
-  - RubyCritic::Configuration#suppress_ratings
-  - RubyCritic::RakeTask#name
-  - RubyCritic::RakeTask#options
-  - RubyCritic::RakeTask#paths
-  - RubyCritic::RakeTask#verbose
-DuplicateMethodCall:
-  exclude:
-  - RubyCritic::Analyser::Churn#run
-  - Parser::AST::Node#module_name
-TooManyStatements:
-  exclude:
-  - RubyCritic::RakeTask#initialize
-  - RubyCritic::Analyser::Complexity#run
-  - Parser::AST::Node#get_module_names
-  - RubyCritic::Analyser::FlaySmells#run
-  - RubyCritic::Cli::Application#execute
-  - RubyCritic::Cli::Options#parse
-  - RubyCritic::CommandFactory#self.command_class
-  - RubyCritic::Configuration#set
-  - RubyCritic::Generator::Html::CodeFile#render
-  - RubyCritic::Reporter#self.report_generator_class
-  - RubyCritic::SourceLocator#deduplicate_symlinks
-FeatureEnvy:
-  exclude:
-  - Parser::AST::Node#module_name
-  - Parser::AST::Node#module_name
-  - Parser::AST::Node#recursive_children
-  - RubyCritic::Analyser::ReekSmells#add_smells_to
-  - RubyCritic::Analyser::ReekSmells#create_smell
-  - RubyCritic::ViewHelpers#smell_location_path
-  - RubyCritic::Generator::HtmlReport#create_directories_and_files
-  - RubyCritic::SourceLocator#deduplicate_symlinks
-NestedIterators:
-  exclude:
-  - Parser::AST::Node#recursive_children
-  - RubyCritic::Analyser::FlaySmells#run
-  - RubyCritic::Cli::Options#parse
-  - RubyCritic::Generator::HtmlReport#create_directories_and_files
-UtilityFunction:
-  exclude:
-  - RubyCritic::Analyser::FlaySmells#cost
-  - RubyCritic::Analyser::FlaySmells#paths_to_analysed_modules
-  - RubyCritic::Analyser::FlaySmells#smell_locations
-  - RubyCritic::Analyser::FlogSmells#type
-  - RubyCritic::Analyser::ReekSmells#smell_locations
-  - RubyCritic::Cli::Application#print
-  - RubyCritic::AnalysedModulesCollection#limited_cost_for
-  - RubyCritic::Generator::Html::SmellsIndex#analysed_module_names
-  - RubyCritic::Generator::HtmlReport#copy_assets_to_report_directory
-  - RubyCritic::SourceControlSystem::Git#date_of_last_commit
-  - RubyCritic::SourceControlSystem::Git#head_reference
-  - RubyCritic::SourceControlSystem::Git#revisions_count
-  - RubyCritic::SourceControlSystem::Git#stashes_count
-  - RubyCritic::SourceControlSystem::Mercurial#date_of_last_commit
-  - RubyCritic::SourceControlSystem::Mercurial#revisions_count
-TooManyInstanceVariables:
-  exclude:
-  - RubyCritic::Cli::Options
-ControlParameter:
-  exclude:
-  - RubyCritic::CommandFactory#self.command_class
-UncommunicativeParameterName:
-  exclude:
-  - RubyCritic::AnalysedModule#to_json
-  - RubyCritic::Location#to_json
-  - RubyCritic::Rating#to_json
-  - RubyCritic::Smell#to_json
-  - Theon # This is needed for the tests to pass
-ClassVariable:
-  exclude:
-  - RubyCritic::SourceControlSystem::Base
-BooleanParameter:
-  exclude:
-  - RubyCritic::Config#self.respond_to_missing?

data/.travis.yml

@@ -1,29 +0,0 @@
-sudo: false
-language: ruby
-cache:
-  bundler: true
-before_install:
-  - gem install bundler
-matrix:
-  include:
-    - rvm: 2.1.0
-    - rvm: 2.1
-    - rvm: 2.2
-    - rvm: 2.3
-    - rvm: 2.4
-    - rvm: 2.5
-    - rvm: ruby-head
-    - rvm: jruby-9.1.8.0
-      env: JRUBY_OPTS='--debug' # get more accurate coverage data
-    - rvm: rbx-3
-  allow_failures:
-    - rvm: ruby-head
-    - rvm: jruby-9.1.8.0
-    - rvm: rbx-3
-  fast_finish: true
-
-script:
-  - bundle exec rake test
-  - bundle exec cucumber features --format progress --color
-  - bundle exec rake reek
-  - bundle exec rubocop

data/.yardopts

@@ -1,5 +0,0 @@
---no-private
---use-cache
---asset images
-lib/**/*.rb -
-README.md LICENSE.txt CHANGELOG.md

data/docs/building-own-code-climate.md

@@ -1,156 +0,0 @@
-# Building your own Code Climate
-
-## Installing Jenkins
-
-There are [official guides for installing Jenkins][1] on pretty much any platform. After following the most suitable one, Jenkins should be running on the Build Server (your machine or AWS, for example).
-
-From this point forward, everything should be installed under the Jenkins user account on the Build Server. Switching user accounts can be achieved by running the Switch User command:
-
-```bash
-$ sudo su - jenkins
-```
-
-In the likely event that you don't know your Jenkins user's password, run the following command to change it:
-
-```bash
-$ sudo passwd jenkins
-```
-
-## Installing Ruby
-
-There are many different [ways to install Ruby][2], RVM and rbenv being the two most popular ones. RVM has a nice [guide on using RVM with Jenkins][3]. Regardless of what you choose, you should now have Ruby running on the Build Server and be able to install any gems.
-
-Ensure that everything is working correctly by running the following command:
-
-```bash
-$ ruby --version
-```
-
-## Installing gems
-
-You should install two gems after installing Ruby: Bundler and RubyCritic. You can do so with the following command:
-
-```bash
-$ gem install bundler rubycritic
-```
-
-## Installing Git
-
-Next up, Git should be installed since Jenkins needs it to be able to clone your repositories in order to analyse them. [This is the installation guide recommended][4] to install Git.
-
-Ensure that everything is working correctly by running the following command:
-
-```bash
-$ git --version
-```
-
-## Generating SSH Keys
-
-SSH keys are a way to identify trusted computers without involving passwords. GitHub has an excellent guide on [generating SSH keys][5] which you should definitely follow.
-
-However, you may want to create a GitHub account just for your Jenkins user. The alternative requires you to add the new SSH Key to your account which, from a security standpoint, is probably a bad idea.
-
-Ensure that everything is working correctly by running the following command:
-
-```bash
-$ ssh -T git@github.com
-```
-
-## Configuring Jenkins
-
-Jenkins should be running automatically after being installed. The Jenkins UI should be accessible at `http://localhost:8080/` in your browser. The next few steps all take place in that UI.
-
-### Enabling Security
-
-By default Jenkins is not secure which means anyone is able to run commands on the Build Server and access your private projects. There are many [ways to secure Jenkins][6], but the simplest one is standard authentication with a username and password.
-
-From the main page, head to `Manage Jenkins` and then to `Configure Global Security` where the option `Enable security` should be checked. Still on the same page, select `Jenkins' own user database` under `Security Realm` and leave `Allow users to sign up` enabled for now.
-
-After configuring these options, a new `sign up` link should appear in the top right corner of every page. After signing up and returning to the `Configure Global Security` page where you were before, it's time to set up some restrictions. The easiest way to do so is to select the option `Logged-in users can do anything` instead of the usual `Anyone can do anything` under `Authorization` and then deselect the option `Allow users to sign up`.
-
-Ensure that everything is working correctly by logging out and logging in again. If you have any problems after these steps and can no longer access Jenkins, you can [reset its security settings][7] and try again.
-
-### Installing Plugins
-
-Installing a Jenkins Plugin is extremely easy. All you have to do is proceed to `Manage Jenkins`, go to `Manage Plugins`, select the `Available` tab and then check the desired plugin.
-
-To build your own Code Climate, three plugins are needed:
-
-  * [GitHub][8], which triggers jobs when you push to a GitHub repository.
-
-  * [Git][9], which allows cloning Git repositories.
-
-  * [HTML Publisher][10], which persists RubyCritic's reports and creates a web interface to access them.
-
-However, you can install many other plugins that will improve your Build server, like:
-
-  * [Jenkins ci skip][11], which skips a build when `[ci skip]` is added to a commit's message.
-
-## Creating Your First Job
-
-Finally, it's time to set up the job that will run in the Build Server after every push. Head to the main page and then to `New Item`. Give the job a name (like the name of your project) and select the option `Build a free-style software project`. Clicking the `OK` button will create the job and take you to the configuration page for that job.
-
-Under `Source Code Management` select `Git` and enter your project's repository URL. If your project is private, then you need to set up Jenkins' credentials so that GitHub can authorize it. This was the reason for setting up Jenkins' SSH key beforehand. Now all that has to be done is to click the `Add` button on the far right, pick the `kind` of credentials `SSH Username with private key` and select the `Private key` option `from the Jenkins master ~/.ssh`. Confirm these new credentials by clicking another `Add` button.
-
-Under `Branches to build` you can enter one or more branches that you want Jenkins to build against. The default is `*/master` but you can leave the `branch` field blank so that Jenkins builds against any changed branch.
-
-Under `Build Triggers` select `Build when a change is pushed to GitHub`, and start configuring the `Build` script. Click the dropdown `Add build step`, select the `Execute shell` option and in the new textarea enter the script to be run after every push. The possibilities here are endless. You could:
-
-  * Build a Continuous Integration server like Travis. To do so, the script could consist in just the following commands:
-
-  ```bash
-  bundle
-  rake
-  ```
-
-  These commands would install all the gems defined in your project's Gemfile and run the project's tests.
-
-  If you had installed Ruby through RVM, your project was a gem and you wished to test it using different, stable Ruby versions, you might change the script to something like this:
-
-  ```bash
-  #!/bin/bash
-  rvm use 1.9.3
-  bundle
-  rake
-  rvm use 2.1
-  bundle
-  rake
-  ```
-
-  Please note that the first line specifies bash as the shell that runs the script and is **necessary** for the script to successfully run.
-
-  * Build a service like Code Climate using the RubyCritic gem. In that case, the script could consist in just the following command:
-
-  ```bash
-  rubycritic app lib
-  ```
-
-  However, Jenkins isolates and cleans the workspace after every build thus making it necessary to use the HTML Publisher plugin (previously installed) to persist the reports generated by RubyCritic.
-
-  Under `Post-build Actions` select `Publish HTML reports`, enter `tmp/rubycritic/` as the `HTML directory to archive`, `overview.html` as the `Index page` and give a title to the report. If you select the option `Keep past HTML reports`, you'll be able to access previous RubyCritic reports, giving you more insight into where your project has been and where it is heading.
-
-Finally, click the `Save` button to save your job configuration. You can try out your build right away by clicking the `Build Now` button.
-
-### Failing fast: the `--minimum-score` option
-
-The CLI option `--minimum-score` makes `rubycritic` return the exit status according to the calculated score: it returns an error exit status if the score is below the set minimum. A helpful message is also printed. This allows your CI job to fail on too-low scores.
-
-## Setting Up A GitHub Service
-
-The last step is to set up GitHub integration so that a push triggers a new job in the Build Server. You’ll need admin access to your project's repository to be able to change its settings. On the repository page navigate to `Settings`, `Webhooks & Services` and click the `Add service` button. Select the `Jenkins (GitHub plugin)` options and set the `Jenkins hook url`.
-
-This URL is the same as the one you use to access the Jenkins UI followed by `/github-webhook/`. On AWS, for example, your URL could look something like `http://ec2-12-34-567-890.amazonaws.com:8080/github-webhook/`.
-
-And you're finally done! After every push to GitHub your Build Server should run RubyCritic and present its results, very much like Code Climate!
-
-[1]: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins
-[2]: https://www.ruby-lang.org/en/installation/
-[3]: https://rvm.io/integration/jenkins
-[4]: http://git-scm.com/book/en/Getting-Started-Installing-Git
-[5]: https://help.github.com/articles/generating-ssh-keys
-[6]: https://wiki.jenkins-ci.org/display/JENKINS/Securing+Jenkins
-[7]: https://wiki.jenkins-ci.org/display/JENKINS/Disable+security
-[8]: https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin
-[9]: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
-[10]: https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin
-[11]: https://github.com/banyan/jenkins-ci-skip-plugin

data/docs/core-metrics.md

@@ -1,72 +0,0 @@
-# Core Metrics, Score and Rating
-
-RubyCritic wraps around static analysis gems such as [Reek][2], [Flay][3] and [Flog][4] to provide a quality report of your Ruby code.
-
-Each of these gems are internally wrapped as an **Analyser**, with a collection of **AnalysedModule**s, which give us calculations of key metrics.
-The most important ones are **churn**, **complexity**, **cost** and **rating**.
-
-The output of RubyCritic will give you four values to help you judge your code's _odorousness_:
-
-- [**Score**](#score): A generic number representing overall quality of the analysed code
-- [**Churn**](#churn-and-complexity): Number of times a file was changed
-- [**Complexity**](#churn-and-complexity): Amount of _pain_ in your code
-- [**Rating**](#rating): The grade assigned to a file
-
-RubyCritic's **rating** system was inspired by Code Climate's, you can [read more about how that works here][1].
-Note that the global **score** is fairly different from Code Climate's GPA, although it serves the same purpose.
-
-## Score
-
-Is a value that ranges from 0 to 100, where higher values are better (less code smells detected) and is intended to provide a quick insight about the overall code quality.
-
-This is basically an average of the calculated [cost](#cost) of each file.
-There is a [threshold][6] to avoid very bad modules from having excessive impact.
-
-## Churn and complexity
-
-Churn is very simple to calculate - it is the number of times the file was committed.
-
-Complexity is the output of [Flog][4]. You can [read more about how it works][7], but here's a quick summary:
-
-> It works based on counting your code's ABCs:
->
-> A - Assignments. When more objects are assigned, the complexity goes up - foo = 1 + 1.
->
-> B - Branches. When code branches, there are multiple paths that it might follow. This also increases it's complexity.
->
-> C - Calls. When code calls other code, the complexity increases because they caller and callee are now connected. A call is both a method call or other action like eval or puts.
->
-> All code has assignments, branches, and calls. Flog's job is to check that they aren't used excessively or abused.
-
-Both **churn** and **complexity** are presented as a chart:
-
-![RubyCritic overview screenshot](/images/churn-vs-complexity.png)
-
-Each file is represented by a dot. **The closer they are to the bottom-left corner, the better.**
-But keep in mind that you cannot reduce churn (well... not unless you re-write your repo's history :neckbeard:), so try to keep the dots as close to the bottom as possible.
-Chad made a nice [summary if you want to know more][8] about the meaning behind each quadrant.
-
-
-## Rating
-
-This is a letter from `A` to `F`, `A` being the best. This serves as a baseline to tell you how *smelly* a file is.
-Generally `A`'s & `B`'s are good enough, `C`'s serve as a warning and `D`'s & `F`'s are the ones you should be fixing.
-
-**Rating** is simply [a conversion][5] from the calculated **cost** to a letter.
-
-![RubyCritic code index screenshot](/images/rating.png)
-
-### Cost
-
-The definition of this **cost** varies from tool to tool, but it's always a non-negative number, with high values indicating worse smells.
-The **complexity** of a file also (slightly) affects its final cost.
-
-
-[1]: https://gist.github.com/brynary/21369b5892525e1bd102
-[2]: https://github.com/troessner/reek
-[3]: https://github.com/seattlerb/flay
-[4]: https://github.com/seattlerb/flog
-[5]: https://github.com/whitesmith/rubycritic/blob/master/lib/rubycritic/core/rating.rb
-[6]: https://github.com/whitesmith/rubycritic/blob/master/lib/rubycritic/core/analysed_modules_collection.rb
-[7]: http://www.railsinside.com/tutorials/487-how-to-score-your-rails-apps-complexity-before-refactoring.html
-[8]: https://github.com/chad/turbulence#hopefully-meaningful-metrics

data/docs/jenkins-pr-reviews.md

@@ -1,64 +0,0 @@
-# Making Jenkins review Pull Requests
-
-## Installing Jenkins and setting up RubyCritic
-
-There is a step-by-step tutorial on how to set up Jenkins in [`building-own-code-climate.md`](./building-own-code-climate.md).
-
-### Installing required plugins
-
-Installing a Jenkins Plugin is extremely easy. All you have to do is proceed to `Manage Jenkins`, go to `Manage Plugins`, select the `Available` tab and then check the desired plugin.
-
-For creating comments on PRs we are going to use the [Violation Comments to GitHub Jenkins Plugin](https://github.com/jenkinsci/violation-comments-to-github-plugin).
-
-## Configuring the project
-
-The Violation plugin has parsers for many different formats, and the GoLint one is compatible with the `lint` format created by RubyCritic.
-We're assuming that you use a `Jenkinsfile` for creating a pipeline, but the approach can be adapted to other scenarios.
-
-
-```groovy
-pipeline {
-  agent any
-
-  stages {
-    stage('Build') {
-      steps {
-        // Install gems etc.
-      }
-    }
-    stage('Test') {
-      steps {
-        parallel tests: { // We are running tests and code_checks in parallel to shorten build times
-          sh 'bundle exec rspec'
-        },
-        code_checks: {
-          sh 'bundle exec rubycritic -f lint'
-        }
-      }
-    }
-    stage('Package / Deploy') {
-      steps {
-        parallel deploy: {
-          // Create Docker image / deploy via Capistrano / ...
-        },
-        publish_code_review: {
-          step([
-            $class: 'ViolationsToGitHubRecorder',
-            config: [
-              repositoryName: 'your_project_name',
-              pullRequestId: env.CHANGE_ID, // The CHANGE_ID env variable will be set to the PR ID by Jenkins
-              createSingleFileComments: true, // Create one comment per violation
-              commentOnlyChangedContent: true, // Only comment on lines that have changed
-              keepOldComments: false,
-              violationConfigs: [
-                [ pattern: '.*/lint\\.txt$', parser: 'GOLINT', reporter: 'RubyCritic' ], // RubyCritic will output a lint.txt file in GoLint compatible format
-              ]
-            ]])
-        }
-      }
-    }
-  }
-}
-```
-
-For further information, check out the documentation of the [Violation Comments to GitHub Jenkins Plugin](https://github.com/jenkinsci/violation-comments-to-github-plugin).