critical-path-css-rails 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8775db565ae10bb4b743f5681dcdab51e8ce9f83
-  data.tar.gz: 91af5fc536b35c5c91dc1e7e278fe8586bf3a07e
+  metadata.gz: 1a1d007d5a2b3ddad015852c79fa46b2f4848a42
+  data.tar.gz: af3d944a516625a45d35592e9f2fe502ae5f7582
 SHA512:
-  metadata.gz: f837d78b8e96facc34a2c1f6f330f07d09fd8ebf4371511b4817e8c7686c09cc32e6fba17dc295143a2aeef9b77c114486edf670dd8e2627075297cc7f34e755
-  data.tar.gz: d3e0e3a9a78765572b80bb40ab7b7944b7ae93e493135ad578f901b5e56040bc9bf4bc3c69eff36c589dbfa4b09fcaa71ffd1c65ae4cbd8b6fb9572ea16e2390
+  metadata.gz: 0a36f37b53c16686f15cec91ab5da1f23f012375b2496f57950eb2979c20c9cb7015252609de7788cf188dd27dfe1ef359bb525f81f54de527841d051e627501
+  data.tar.gz: e3da5b537e8828ef9ba77f5e7965cd2949e7a3b403dec1dfcc94885958b9d2d67a72b7ced2ed8e9421c04a5fa60d094bb13ffe097a9b005295670189a31f23e7

data/.rubocop_todo.yml

@@ -1,12 +1,12 @@
 # This configuration was generated by
 # `rubocop --auto-gen-config`
-# on 2015-10-03 13:56:01 -0500 using RuboCop version 0.34.1.
+# on 2015-10-20 18:42:42 -0500 using RuboCop version 0.34.1.
 # The point is for the user to remove these configuration records
 # one by one as the offenses are removed from the code base.
 # Note that changes in the inspected code, or installation of new
 # versions of RuboCop, may require this file to be generated again.
 
-# Offense count: 2
+# Offense count: 3
 # Configuration parameters: AllowURI, URISchemes.
 Metrics/LineLength:
-  Max: 86
+  Max: 91

data/BACKLOG.md

@@ -6,5 +6,5 @@
 ## Features
 - Allow the user to pass arguments to Penthouse.js, i.e. Viewport size, etc. For a list of the configurable options, please see [Penthouse](https://github.com/pocketjoso/penthouse)
 - Improve installation process, if necessary
-- Improve manual processes, if possible (i.e having to run the rake task to generate the the critical CSS)
+- Improve manual processes, if possible (i.e having to run the rake task to generate the critical CSS)
 - Improve implementation. Is their a better solution then using Rails.cache?

data/README.md

@@ -47,11 +47,11 @@ First, you'll need to configue a few things in the YAML file: `config/critical_p
 
 Before generating the CSS, ensure that your application is running (viewable from a browser) and the main CSS file exists. Then in a separate tab, run the rake task to generate the critical CSS.
 
-If your main CSS file does not already exist, and you are using the Asset Pipeline, generate the main CSS file.
+If you are using the Asset Pipeline, precompiling the assets will generate the critical CSS after the assets are precompiled.
 ```
 rake assets:precompile
 ```
-Generate the critical path CSS:
+Else you can generate the critical CSS manually using the below task:
 ```
 rake critical_path_css:generate
 ```

data/lib/critical_path_css/rails/version.rb

@@ -1,6 +1,6 @@
 module CriticalPathCSS
   module Rails
-    VERSION = '0.2.0'
+    VERSION = '0.2.1'
     PENTHOUSE_VERSION = '0.3.4'
   end
 end

data/lib/tasks/critical_path_css.rake

@@ -6,3 +6,5 @@ namespace :critical_path_css do
     CriticalPathCss.generate
   end
 end
+
+Rake::Task['assets:precompile'].enhance { Rake::Task['critical_path_css:generate'].invoke }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: critical-path-css-rails
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Michael Misshore
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-03 00:00:00.000000000 Z
+date: 2015-10-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: phantomjs