All Versions
141
Latest Version
Avg Release Cycle
66 days
Latest Release
67 days ago

Changelog History
Page 10

  • v2.0.3 Changes

    April 06, 2015
    • (mvz) Make NestedIterators handle super with arguments
    • (mvz) Handle shadow block arguments
    • 👍 (CoralineAda) Allow all formatters to support -U (wiki links)
    • 0️⃣ (tuexss) Make defaults transparent in help message

  • v2.0.2 Changes

    March 15, 2015
    • (troessner) Fix version command

  • v2.0.1 Changes

    March 03, 2015

  • v2.0.0 Changes

    February 09, 2015
    • 🔨 (troessner) Revise, improve & refactor our Rspec matcher and remove smell_of
    • (guilhermesimoes) Fix generating HTML report
    • (mvz) Re-organize CLI options
    • (maser) Fix file arguments without TTY
    • (marcofognog) Make NestedIterator not break if iterator is called on super
    • 🔨 (troessner) Revamp & refactor our rake task

  • v1.6.3 Changes

    January 15, 2015
    • 💎 (mvz) Support Ruby 2.2

  • v1.6.2 Changes

    January 13, 2015
    • (mvz) Fix rake task bug when no config file was given explicitly.
    • (troessner) Run on working directory when no source is given.

  • v1.6.1 Changes

    December 20, 2014
    • (mvz) Fix regression in rake task: Provide alias for backward compatibility

  • v1.6.0 Changes

    December 27, 2014
    • 🔧 (troessner) Revise configuration handling: 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 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 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'
    • (mvz) Handle nil-block in iterators

  • v1.5.1 Changes

    December 05, 2014
    • 👍 (mvz) Fix support for empty block in NestedIterators
    • ⚡️ (mvz) Update minimum required Ruby version to 1.9.3
    • 👍 (chastell) Fix support for required keyword arguments

  • v1.5.0 Changes

    December 01, 2014
    • 📜 (mvz) Parse with the parser gem
    • (mvz) Add ModuleInitialize smell