blue_steel 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5380af4e3107116fccabf7cdf28f97e6e579f8bf
-  data.tar.gz: 7246764080dc351c0f0a0ca840a8e74ce7705d90
+  metadata.gz: a51a97a53da0841c3a75a905504c25fd3353ad02
+  data.tar.gz: c7ba6e274bdb850ae6503fa990d2a46dbc398a6d
 SHA512:
-  metadata.gz: bca8b7184a076d00d9411d9125c1a5f13089f8cc5124f5d78a3f752b2a494c6ec8500a5d9e56e5c9c4620e45fab196ad1d5116c2003ba5d60b6d1c76251ee619
-  data.tar.gz: 711a4abcb66fcba2901bdc5e8e2f4683f7a4a442809bce0ef423c86253d262740a6bb679f2eda6e6a7b5d432c0091dc7dbd2d36327d79f32f065a6c10867ac5c
+  metadata.gz: ed3a1db32e443594a9ea54deaf5e86ff566c236902c0601c096b18ed286391d47be6f08744464cfe80622bae850be80f5833a763de5864dd27d8663f4c2689a2
+  data.tar.gz: 4660612e561bdcb2c79e9a1c6bcfa6ec93a2f99939c58d8f77a4e3abbcf9a22bc5d61f14e7baa782b86f61509273af20678863eea964a477ff5730ae56bb08bd

data/README.md

@@ -1,15 +1,10 @@
-# Coding In Style
+# BlueSteel
 
 We all recognize that style matters, and particularly that having _a_ consistent
 style matters more than _my_ or _your_ particular preference for a style (See
 Sandi Metz's _Looks Matter_). This repository contains the Apartment List style.
 
-# Installation
-
-See each directory for installation in that language:
-- [Ruby](/ruby)
-
-# Changing Style
+### Changing Style
 
 Thrash is anathema to consistency, so we are making it very difficult to change
 styles. Consider it a Constitution. We all agreed on it hundreds of years ago,
@@ -20,3 +15,37 @@ Since we're intentionally making it difficult to change, I'm only going to give
 you one criterion to consider when you want to propose a change:
 
 1. The style is probably not going to change, and that's ok!
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'blue_steel'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install blue_steel
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/blue_steel.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/{ruby/blue_steel/blue_steel.gemspec → blue_steel.gemspec}

@@ -10,7 +10,7 @@ Gem::Specification.new do |spec|
   spec.email         = ["cirmas@apartmentlist.com"]
 
   spec.summary       = %q{Apartment List's internal coding style guide}
-  spec.homepage      = "https://github.com/apartmentlist/style/tree/master/ruby/blue_steel"
+  spec.homepage      = "https://github.com/apartmentlist/blue_steel"
   spec.license       = "MIT"
 
   spec.files         = `git ls-files -z`.split("\x0").reject do |f|

data/lib/blue_steel/version.rb

@@ -0,0 +1,3 @@
+module BlueSteel
+  VERSION = '0.1.2'.freeze
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: blue_steel
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Cameron Irmas
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2017-08-08 00:00:00.000000000 Z
+date: 2017-09-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rubocop-git
@@ -87,26 +87,21 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".gitignore"
+- ".rubocop.yml"
+- Gemfile
+- LICENSE.txt
 - README.md
-- ruby/README.md
-- ruby/blue_steel/.gitignore
-- ruby/blue_steel/.rubocop.yml
-- ruby/blue_steel/Gemfile
-- ruby/blue_steel/LICENSE.txt
-- ruby/blue_steel/README.md
-- ruby/blue_steel/Rakefile
-- ruby/blue_steel/bin/console
-- ruby/blue_steel/bin/setup
-- ruby/blue_steel/blue_steel.gemspec
-- ruby/blue_steel/global.yml
-- ruby/blue_steel/lib/blue_steel.rb
-- ruby/blue_steel/lib/blue_steel/railtie.rb
-- ruby/blue_steel/lib/blue_steel/version.rb
-- ruby/blue_steel/lib/tasks/style.rake
-- ruby/global.yml
-- ruby/lib/tasks/style.rake
-- ruby/sample.yml
-homepage: https://github.com/apartmentlist/style/tree/master/ruby/blue_steel
+- Rakefile
+- bin/console
+- bin/setup
+- blue_steel.gemspec
+- global.yml
+- lib/blue_steel.rb
+- lib/blue_steel/railtie.rb
+- lib/blue_steel/version.rb
+- lib/tasks/style.rake
+homepage: https://github.com/apartmentlist/blue_steel
 licenses:
 - MIT
 metadata: {}

data/ruby/README.md

@@ -1,52 +0,0 @@
-# Installation
-
-1. Add these gems to your `Gemfile`, most likely just in the `development`
-   group:
-
-    - [`rubocop`](https://github.com/bbatsov/rubocop) - The base rules, more or
-      less agreed upon by the Ruby community.
-    - [`rubocop-rspec`](https://github.com/backus/rubocop-rspec) - More
-      customized rules for the `spec/` directory, where RSpec's DSL is more
-      valuable than "normal" Ruby style.
-    - [`rubocop-git`](https://github.com/m4i/rubocop-git) - This lets you run
-      style checks on just your changes, so you're not responsible for a whole
-      history of accumulated style mishaps.
-
-2. Copy the minimal Rubocop configuration to your repository:
-
-    ```
-    cp style/ruby/sample.yml my_app/.rubocop.yml
-    ```
-
-    This file does little more than inherit from `global.yml`, which allows us
-    to configure and change global style in a single place.
-
-3. Add this pattern to your repo's `.gitignore`:
-
-    ```
-    .rubocop-http*yml
-    ```
-
-    When Rubocop inherits from a URL, it downloads and caches the file locally
-    so you don't have to hit the network every time. There's no need for that
-    cache to be committed to the repository or clutter `git status`.
-
-4. Install the Rake tasks:
-
-    ```
-    cp style/ruby/lib/tasks/style.rake my_app/lib/tasks/
-    ```
-
-    This provides you three Rake tasks:
-    - `style:branch` - Runs style checks only on your diff from `master`
-    - `style:all` - Runs all style checks
-    - `style:count` - Prints counts of all style violations
-
-5. Set your `Rakefile` default to include style checks:
-
-    ```
-    task default: %i[spec style:branch]
-    ```
-
-    Style checks will only run if specs passed, so you don't have to worry about
-    pretty code until you have working code.

data/ruby/blue_steel/README.md

@@ -1,51 +0,0 @@
-# BlueSteel
-
-We all recognize that style matters, and particularly that having _a_ consistent
-style matters more than _my_ or _your_ particular preference for a style (See
-Sandi Metz's _Looks Matter_). This repository contains the Apartment List style.
-
-### Changing Style
-
-Thrash is anathema to consistency, so we are making it very difficult to change
-styles. Consider it a Constitution. We all agreed on it hundreds of years ago,
-and though everyone has some gripes with it, it's pretty good and we're leaving
-it alone.
-
-Since we're intentionally making it difficult to change, I'm only going to give
-you one criterion to consider when you want to propose a change:
-
-1. The style is probably not going to change, and that's ok!
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'blue_steel'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install blue_steel
-
-## Usage
-
-TODO: Write usage instructions here
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/blue_steel.
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/ruby/blue_steel/lib/blue_steel/version.rb

@@ -1,3 +0,0 @@
-module BlueSteel
-  VERSION = '0.1.1'.freeze
-end

data/ruby/global.yml

@@ -1,87 +0,0 @@
-require: rubocop-rspec
-
-AllCops:
-  # Ruby files that are otherwise missed, since default is just *.rb
-  Include:
-    - config.ru
-    - Gemfile
-    - Rakefile
-  # Files that aren't helpful to check, even if they're Ruby
-  Exclude:
-    - 'db/schema.rb'
-    - 'node_modules/**/*'
-
-CollectionMethods:
-  PreferredMethods:
-    collect: map
-    inject: reduce
-    # Avoid confusion with ActiveRecord methods
-    find_all: select
-    find: detect
-
-FileName:
-  Exclude:
-    - Guardfile # Like Rakefile
-
-# Default is 79, a whole 1.25% reduction in usable space!
-LineLength:
-  Max: 80
-
-# RSpec's DSL leads to long blocks, and that's ok
-Metrics/BlockLength:
-  ExcludedMethods: ['context', 'describe', 'shared_examples']
-
-# Don't require underscores in long numbers, eg. 123_456_789.
-# We often have IDs, not "numbers".
-NumericLiterals:
-  Enabled: false
-
-# We've set RSpec to infer_spec_type_from_file_location!, but RuboCop doesn't
-# have access to that config. Rather than have to tag everything `type: :view`,
-# just ignore the cop for those specs.
-RSpec/DescribeClass:
-  Exclude:
-    - spec/views/**/*_spec.rb
-
-# The default is not_to, but we've historically used to_not basically 100% of
-# the time. There doesn't appear to be a particular reason one is better, and
-# it's not worth changing.
-RSpec/NotToNot:
-  EnforcedStyle: to_not
-
-# Don't force single line blocks to name their block arguments things like
-# |a, e| for accumulator, element. Eg:
-#
-#   things.reduce { |a, e| ... }
-#
-# We have more semantic context than Rubocop, so there's no reason it should be
-# dictating our variable names.
-SingleLineBlockParams:
-  Enabled: false
-
-# Migrations are particularly self-explanatory, so there's very little reason to
-# write class documentation for them.
-Style/Documentation:
-  Exclude:
-    - db/migrate/*.rb
-
-# This requires us to parenthesize simple things like (a % 10).zero?, which
-# we've never done and find cumbersome without improving clarity. The community
-# doesn't appear to have a clear reason why one is superior.
-Style/NumericPredicate:
-  Enabled: false
-
-Style/PercentLiteralDelimiters:
-  PreferredDelimiters:
-    # Prefer [] for things that are arrays
-    '%i': '[]'
-    '%I': '[]'
-    '%w': '[]'
-    '%W': '[]'
-    # Prefer () otherwise
-    '%':  '()'
-    '%q': '()'
-    '%Q': '()'
-    '%r': '()'
-    '%s': '()'
-    '%x': '()'

data/ruby/lib/tasks/style.rake

@@ -1,34 +0,0 @@
-# frozen_string_literal: true
-
-# No need to have Rubocop in production, so be careful loading it.
-begin
-  require 'rubocop/git/cli'
-rescue LoadError
-  puts <<-MSG
-    Warning: RuboCop::Git is not available.
-    Run `gem install rubocop-git` or add it to your Gemfile
-  MSG
-end
-
-namespace :style do
-  desc 'Run style checks for the entire repository'
-  task all: :environment do
-    system('rubocop --display-cop-names')
-  end
-
-  desc 'Run style checks on your diff from `master`'
-  task branch: :environment do
-    RuboCop::Git::CLI.new.run(%w[--display-cop-names master])
-  end
-
-  desc 'Print total violation counts'
-  task count: :environment do
-    puts `
-      rubocop --display-cop-names |
-      grep -oE '[CW]: [^:]+'      | # Extract "C: Thing/YouBroke"
-      sort                        |
-      uniq -c                     |
-      sort -rn
-    `
-  end
-end

data/ruby/sample.yml

@@ -1,2 +0,0 @@
-inherit_from:
-  - https://raw.githubusercontent.com/apartmentlist/style/master/ruby/global.yml