Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Jan 17, 2015
  1. Upload docs to S3.

    authored
Commits on Jan 10, 2015
  1. Removed libyaml installation.

    authored
    This doesn't fix anything, lets just wait for a new Rbx release.
  2. Install libyaml on Travis.

    authored
    Lets see if _this_ fixes the failures.
  3. Revert "Switch back to non containers on Travis."

    authored
    This reverts commit af5d7eb.
    
    This doesn't stop the Travis failures.
Commits on Jan 9, 2015
  1. Switch back to non containers on Travis.

    authored
    This seems to be causing random Rbx errors that are unrelated to ruby-lint
    itself. Not sure if this will fix it, but we'll see.
  2. Run tests on MRI 2.2.

    authored
  3. Update to parser 2.2.

    authored
  4. Release 2.0.3

    authored
  5. Merge pull request #140 from seancaffery/remove-union

    authored
    Replace Array#| with Array#+
  6. Sean Caffery

    Replace Array#| with Array#+

    seancaffery authored seancaffery committed
    This is primarily for performance reasons. It yields around a 23%
    improvement on a file with 300 violations.
Commits on Jan 8, 2015
Commits on Dec 22, 2014
  1. Merge pull request #139 from braingourmets/task/travis-performance

    authored
    [TASK] Configure Travis for better build performance
  2. Oliver Klee

    [TASK] Configure Travis for better build performance

    oliverklee authored
    Set sudo: false to allow usage of their new container-based infrastructure.
Commits on Aug 27, 2014
Commits on Aug 9, 2014
  1. Merge pull request #136 from allquixotic/fix-issue-133

    authored
    Use #name instead of #to_s when getting the name of constants.
  2. Sean McNamara

    Use #name instead of #to_s when getting the name of constants.

    allquixotic authored
    The only constants that the Inspector should be looking at are of type Module or Class. Both of these built-in types respond to #name, but some gems (such as LibXML) create Modules in such a way that they implement #to_s with one (required) argument, whereas here we only call it with 0 arguments.
    
    In most cases #to_s will be an alias for #name, and #name is really what we want anyway. Aside from that, many core classes and core functionality of Ruby will break if a gem maintainer chooses not to implement #name, whereas not implementing the zero-argument #to_s message appears to have no ill effects outside of causing ruby-lint to raise an exception when generating definitions for these gems.
    
    Fixes [#133](#133).
  3. Merge pull request #134 from allquixotic/new-defs

    authored
    New definitions for various libraries I use.
  4. Don't use anonymous modules for Inspector tests.

    authored
    Anonymous modules don't have names, which prevents the use of Module#name.
Commits on Aug 7, 2014
  1. Sean McNamara
  2. Sean McNamara
  3. Sean McNamara
  4. Sean McNamara
  5. Sean McNamara
  6. Removed integration section from the README.

    authored
    This will be moved over to the Wiki.
  7. Added basic definitions for Mongoid.

    authored
    This currently misses about 80% of everything Mongoid includes due to Mongoid
    using `included` (http://git.io/0V_NGQ). I'll have to look into somehow
    supported this a bit better.
Commits on Aug 6, 2014
  1. Fix scanning for dashed directories.

    authored
    The FileScanner class wasn't properly scanning for files located in a directory
    that used dashes instead of underscores. This in turn would prevent ruby-lint
    from analysing itself due to the usage of lib/ruby-lint (instead of
    lib/ruby_lint).
    
    With this commit I've also taken the liberty of cleaning up the tests for
    FileScanner. These tests now test more specific parts instead of only testing
    the scan method.
Commits on Aug 5, 2014
  1. Analysis for loop keywords.

    authored
    This analysis class checks if certain keywords are used inside blocks/loops or
    not. If this is not the case an error is added.
    
    Ruby reports this kind of usage as a syntax error. Parser doesn't handle this
    and rightfully so. This requires keeping track of two things:
    
    1. Are we in a block?
    2. Are we in a loop that allows next/break?
    
    While the code for this is not too difficult I don't feel this should be handled
    on parser level, thus I've added it to a new analysis class.
    
    This fixes #126.
  2. Merge pull request #127 from bbatsov/patch-1

    authored
    Correct RuboCop name references in the README
  3. Release 2.0.2.

    authored
Something went wrong with that request. Please try again.