thoughtbot--shoulda-matchers/Gemfile.lock

GEM
  remote: https://rubygems.org/
  specs:
    appraisal (2.2.0)
      bundler
      rake
      thor (>= 0.14.0)
    ast (2.4.0)
    byebug (9.1.0)
    coderay (1.1.2)
    diff-lcs (1.3)
    fssm (0.2.10)
    jaro_winkler (1.5.2)
    method_source (0.9.0)
    multi_json (1.12.1)
    parallel (1.17.0)
    parser (2.6.3.0)
      ast (~> 2.4.0)
    pry (0.11.3)
      coderay (~> 1.1.0)
      method_source (~> 0.9.0)
    pry-byebug (3.5.1)
      byebug (~> 9.1)
      pry (~> 0.10)
    pygments.rb (1.1.1)
      multi_json (>= 1.0.0)
    rack (2.0.7)
    rainbow (3.0.0)
    rake (12.3.2)
    redcarpet (3.4.0)
    rspec (3.6.0)
      rspec-core (~> 3.6.0)
      rspec-expectations (~> 3.6.0)
      rspec-mocks (~> 3.6.0)
    rspec-core (3.6.0)
      rspec-support (~> 3.6.0)
    rspec-expectations (3.6.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.6.0)
    rspec-mocks (3.6.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.6.0)
    rspec-support (3.6.0)
    rubocop (0.71.0)
      jaro_winkler (~> 1.5.1)
      parallel (~> 1.10)
      parser (>= 2.6)
      rainbow (>= 2.2.2, < 4.0)
      ruby-progressbar (~> 1.7)
      unicode-display_width (>= 1.4.0, < 1.7)
    rubocop-rails (2.0.0)
      rack (>= 2.0)
      rubocop (>= 0.70.0)
    ruby-progressbar (1.10.1)
    thor (0.20.0)
    unicode-display_width (1.6.0)
    yard (0.9.12)
    zeus (0.15.14)
      method_source (>= 0.6.7)

PLATFORMS
  ruby

DEPENDENCIES
  appraisal (= 2.2.0)
  bundler (~> 1.1)
  fssm
  pry
  pry-byebug
  pygments.rb
  rake (= 12.3.2)
  redcarpet
  rspec (~> 3.6)
  rubocop
  rubocop-rails
  yard
  zeus

BUNDLED WITH
   1.17.2
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`GEM`
Rename failure_message and negative_failure_message * fixes #108 : RSpec 2.10 compatibility * remove unnecessary attr_readr 2013-01-08 12:29:01 -05:00			`remote: https://rubygems.org/`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`specs:`
Upgrade Appraisal to 2.2.0 2018-01-24 00:01:41 -06:00			`appraisal (2.2.0)`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`bundler`
			`rake`
Use the new appraisal executable in 1.0.0.beta1 2014-01-20 11:39:18 -07:00			`thor (>= 0.14.0)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`ast (2.4.0)`
Update Pry and Coderay so Zeus can be run 2017-11-29 12:29:40 -06:00			`byebug (9.1.0)`
			`coderay (1.1.2)`
Update rspec & rspec-rails to 3.6.x This upgrade is mainly so we can use --only-failures which was introduced way back in RSpec 3.3. 2017-07-24 21:15:24 -05:00			`diff-lcs (1.3)`
Manually autogenerate docs Why: * The guard-yard gem doesn't seem to work so well anymore. In fact, the problem is with `yard server` -- it doesn't seem to use our custom template files. To satisfy the above: * Instead of using Guard and guard-yard, use the fssm gem to manually watch various files. * Instead of using `yard server`, run `yard doc`, which does honor our custom template files. * You can run `rake autogenerate_docs` to make this happen; update the README accordingly. [ci skip] 2015-09-23 13:44:42 -06:00			`fssm (0.2.10)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`jaro_winkler (1.5.2)`
Update Pry and Coderay so Zeus can be run 2017-11-29 12:29:40 -06:00			`method_source (0.9.0)`
Mass-update all dev dependencies 2017-01-09 09:55:12 -07:00			`multi_json (1.12.1)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`parallel (1.17.0)`
			`parser (2.6.3.0)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`ast (~> 2.4.0)`
Update Pry and Coderay so Zeus can be run 2017-11-29 12:29:40 -06:00			`pry (0.11.3)`
Update zeus & pry so that we can use Zeus again 2017-07-24 20:54:43 -05:00			`coderay (~> 1.1.0)`
Update Pry and Coderay so Zeus can be run 2017-11-29 12:29:40 -06:00			`method_source (~> 0.9.0)`
			`pry-byebug (3.5.1)`
			`byebug (~> 9.1)`
Use pry-byebug instead of pry-nav 2015-04-03 00:42:53 +09:00			`pry (~> 0.10)`
Mass-update all dev dependencies 2017-01-09 09:55:12 -07:00			`pygments.rb (1.1.1)`
			`multi_json (>= 1.0.0)`
Bring in Rails cops using rubocop-rails After installing Rubocop 0.71, I received this warning: Rails cops will be removed from RuboCop 0.72. Use the `rubocop-rails` gem instead. This commit follows these instructions. [ci skip] 2019-06-07 21:57:40 -06:00			`rack (2.0.7)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`rainbow (3.0.0)`
Upgrade Rake so that Zeus runs 2019-01-29 00:29:46 -07:00			`rake (12.3.2)`
Mass-update all dev dependencies 2017-01-09 09:55:12 -07:00			`redcarpet (3.4.0)`
Update rspec & rspec-rails to 3.6.x This upgrade is mainly so we can use --only-failures which was introduced way back in RSpec 3.3. 2017-07-24 21:15:24 -05:00			`rspec (3.6.0)`
			`rspec-core (~> 3.6.0)`
			`rspec-expectations (~> 3.6.0)`
			`rspec-mocks (~> 3.6.0)`
			`rspec-core (3.6.0)`
			`rspec-support (~> 3.6.0)`
			`rspec-expectations (3.6.0)`
Using RSpec 3 for development. 2014-06-17 01:54:02 -03:00			`diff-lcs (>= 1.2.0, < 2.0)`
Update rspec & rspec-rails to 3.6.x This upgrade is mainly so we can use --only-failures which was introduced way back in RSpec 3.3. 2017-07-24 21:15:24 -05:00			`rspec-support (~> 3.6.0)`
			`rspec-mocks (3.6.0)`
Upgrade rspec 2015-10-07 23:26:48 -06:00			`diff-lcs (>= 1.2.0, < 2.0)`
Update rspec & rspec-rails to 3.6.x This upgrade is mainly so we can use --only-failures which was introduced way back in RSpec 3.3. 2017-07-24 21:15:24 -05:00			`rspec-support (~> 3.6.0)`
			`rspec-support (3.6.0)`
Bring in Rails cops using rubocop-rails After installing Rubocop 0.71, I received this warning: Rails cops will be removed from RuboCop 0.72. Use the `rubocop-rails` gem instead. This commit follows these instructions. [ci skip] 2019-06-07 21:57:40 -06:00			`rubocop (0.71.0)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`jaro_winkler (~> 1.5.1)`
			`parallel (~> 1.10)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`parser (>= 2.6)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`rainbow (>= 2.2.2, < 4.0)`
			`ruby-progressbar (~> 1.7)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`unicode-display_width (>= 1.4.0, < 1.7)`
Bring in Rails cops using rubocop-rails After installing Rubocop 0.71, I received this warning: Rails cops will be removed from RuboCop 0.72. Use the `rubocop-rails` gem instead. This commit follows these instructions. [ci skip] 2019-06-07 21:57:40 -06:00			`rubocop-rails (2.0.0)`
			`rack (>= 2.0)`
			`rubocop (>= 0.70.0)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`ruby-progressbar (1.10.1)`
Upgrade Appraisal to 2.2.0 2018-01-24 00:01:41 -06:00			`thor (0.20.0)`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`unicode-display_width (1.6.0)`
Update locked yard to 0.9.12. (#1068) There's a known vulnerability in 0.9.9. https://nvd.nist.gov/vuln/detail/CVE-2017-17042 2017-12-21 14:17:37 +00:00			`yard (0.9.12)`
Update zeus & pry so that we can use Zeus again 2017-07-24 20:54:43 -05:00			`zeus (0.15.14)`
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb 2015-11-29 18:57:45 -07:00			`method_source (>= 0.6.7)`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00
			`PLATFORMS`
			`ruby`

			`DEPENDENCIES`
Upgrade Appraisal to 2.2.0 2018-01-24 00:01:41 -06:00			`appraisal (= 2.2.0)`
Whoops, don't use Bundler 1.0 2012-09-21 15:19:41 -04:00			`bundler (~> 1.1)`
Manually autogenerate docs Why: * The guard-yard gem doesn't seem to work so well anymore. In fact, the problem is with `yard server` -- it doesn't seem to use our custom template files. To satisfy the above: * Instead of using Guard and guard-yard, use the fssm gem to manually watch various files. * Instead of using `yard server`, run `yard doc`, which does honor our custom template files. * You can run `rake autogenerate_docs` to make this happen; update the README accordingly. [ci skip] 2015-09-23 13:44:42 -06:00			`fssm`
Update zeus & pry so that we can use Zeus again 2017-07-24 20:54:43 -05:00			`pry`
Use pry-byebug instead of pry-nav 2015-04-03 00:42:53 +09:00			`pry-byebug`
Generate docs using YARD 2014-06-19 22:44:06 -06:00			`pygments.rb`
Upgrade Rake so that Zeus runs 2019-01-29 00:29:46 -07:00			`rake (= 12.3.2)`
Generate docs using YARD 2014-06-19 22:44:06 -06:00			`redcarpet`
Update rspec & rspec-rails to 3.6.x This upgrade is mainly so we can use --only-failures which was introduced way back in RSpec 3.3. 2017-07-24 21:15:24 -05:00			`rspec (~> 3.6)`
Simplify Rubocop configuration The original Rubocop configuration was copied from other thoughtbot projects. Of course, Rubocop comes with its own set of default settings. Therefore, we don't need to re-specify settings that it already has -- we only need to specify the ones that we're overriding. Besides this, Rubocop isn't even in the Gemfile, so even though Hound runs on GitHub automatically, it'd be nice to spot style issues as you are editing files. Given this, this commit simplifies the Rubocop configuration and also adds Rubocop to the Gemfile so that you can configure your editor to lint files as you are editing them. 2018-09-12 21:33:48 -06:00			`rubocop`
Bring in Rails cops using rubocop-rails After installing Rubocop 0.71, I received this warning: Rails cops will be removed from RuboCop 0.72. Use the `rubocop-rails` gem instead. This commit follows these instructions. [ci skip] 2019-06-07 21:57:40 -06:00			`rubocop-rails`
Generate docs using YARD 2014-06-19 22:44:06 -06:00			`yard`
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb 2015-11-29 18:57:45 -07:00			`zeus`
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages. 2015-12-23 01:46:29 -05:00
			`BUNDLED WITH`
Update Rubocop & Rubocop config 2019-05-30 00:28:00 -06:00			`1.17.2`