sapling 0.4.1 → 0.4.2

data/README.md

@@ -99,12 +99,12 @@ You can optionally inject your own code for testing if a feature is active. In r
 Client-side Usage
 -----------------
 
-Sapling include a javascript helper which add and remove classes on the HTML element for a given user, based upon the
+Sapling include a javascript helper which adds and removes classes on the HTML element for a given user, based upon the
 features available to that user.
 
-Given the feature `space_chat`, if it is enabled for the given user, the html root will get an class `sapling_feature_space_chat_on`.  If disabled for the given user, the class will be `sapling_feature_space_chat_off`.
+Given the feature `space_chat`, if it is enabled for the given user, the html root will get the class `sapling_feature_space_chat_on`.  If disabled for the given user, the class will be `sapling_feature_space_chat_off`.
 
-To retrieve the class name for a given feature, you can use the `sapling_js_generator.css_container_class(feature)` and `sapling_js_generator.css_toggle_class(feature, on? (boolean) )` helpers in your ERB files.
+To retrieve the class name for a given feature, you can use `sapling.css_class(feature)` and `sapling.css_toggle_class(feature, on? (boolean) )` in your ERB files.
 
 Using the client-side tools, you can define CSS classes which will be visible/invisible when a feature is enabled/disabled.  For example:
 

data/changelog.md

@@ -1,13 +1,7 @@
-API changes in 0.3.0
-====================
-
-When using Sapling in rails, there are some api changes:
-
-  old: feature_active?(feature_name)
-  new: sapling.active?(feature_name,options={})
+0.4.2
+=====
 
-  old: feature_class(feature_name)
-  new: sapling.css_class(feature_name)
+Fixed a install/permissions issue.
 
 0.4.1
 =====
@@ -17,3 +11,14 @@ every override method called. This indicates if the feature would be active
 without the override.
 
 Fixed fatal bug in the Sapling+Rails controller javascript generation.
+
+API changes in 0.3.0
+====================
+
+When using Sapling in rails, there are some api changes:
+
+  old: feature_active?(feature_name)
+  new: sapling.active?(feature_name,options={})
+
+  old: feature_class(feature_name)
+  new: sapling.css_class(feature_name)

data/lib/sapling/version.rb

@@ -1,3 +1,3 @@
 module Sapling
-  VERSION = "0.4.1"
+  VERSION = "0.4.2"
 end

metadata

@@ -1,112 +1,83 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: sapling
-version: !ruby/object:Gem::Version 
-  hash: 13
+version: !ruby/object:Gem::Version
+  version: 0.4.2
   prerelease: 
-  segments: 
-  - 0
-  - 4
-  - 1
-  version: 0.4.1
 platform: ruby
-authors: 
+authors:
 - Shane Brinkman-Davis
 - Jason Strutz
 autorequire: 
 bindir: bin
 cert_chain: []
-
-date: 2012-02-03 00:00:00 -08:00
-default_executable: 
-dependencies: 
-- !ruby/object:Gem::Dependency 
+date: 2012-02-06 00:00:00.000000000Z
+dependencies:
+- !ruby/object:Gem::Dependency
   name: activerecord
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
+  requirement: &70325757393920 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">"
-      - !ruby/object:Gem::Version 
-        hash: 5
-        segments: 
-        - 2
-        - 3
-        version: "2.3"
+    requirements:
+    - - ! '>'
+      - !ruby/object:Gem::Version
+        version: '2.3'
   type: :runtime
-  version_requirements: *id001
-- !ruby/object:Gem::Dependency 
-  name: rspec
   prerelease: false
-  requirement: &id002 !ruby/object:Gem::Requirement 
+  version_requirements: *70325757393920
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: &70325757393320 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
+    requirements:
     - - ~>
-      - !ruby/object:Gem::Version 
-        hash: 19
-        segments: 
-        - 2
-        - 7
-        - 0
+      - !ruby/object:Gem::Version
         version: 2.7.0
   type: :development
-  version_requirements: *id002
-- !ruby/object:Gem::Dependency 
-  name: rails
   prerelease: false
-  requirement: &id003 !ruby/object:Gem::Requirement 
+  version_requirements: *70325757393320
+- !ruby/object:Gem::Dependency
+  name: rails
+  requirement: &70325757392780 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - "="
-      - !ruby/object:Gem::Version 
-        hash: 27
-        segments: 
-        - 2
-        - 3
-        - 12
+    requirements:
+    - - =
+      - !ruby/object:Gem::Version
         version: 2.3.12
   type: :development
-  version_requirements: *id003
-- !ruby/object:Gem::Dependency 
-  name: mocha
   prerelease: false
-  requirement: &id004 !ruby/object:Gem::Requirement 
+  version_requirements: *70325757392780
+- !ruby/object:Gem::Dependency
+  name: mocha
+  requirement: &70325757392300 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        hash: 3
-        segments: 
-        - 0
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :development
-  version_requirements: *id004
-- !ruby/object:Gem::Dependency 
-  name: sqlite3
   prerelease: false
-  requirement: &id005 !ruby/object:Gem::Requirement 
+  version_requirements: *70325757392300
+- !ruby/object:Gem::Dependency
+  name: sqlite3
+  requirement: &70325757391660 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
+    requirements:
     - - ~>
-      - !ruby/object:Gem::Version 
-        hash: 19
-        segments: 
-        - 1
-        - 3
-        - 4
+      - !ruby/object:Gem::Version
         version: 1.3.4
   type: :development
-  version_requirements: *id005
-description: Sapling lets you seed your new features to just a few users at a time. You can change which and how many users are seeded for a feature dynamically by updating the database via the Sapling API. Core features are the ability to seed a feature for specific users and/or a percentage of users.
-email: 
+  prerelease: false
+  version_requirements: *70325757391660
+description: Sapling lets you seed your new features to just a few users at a time.
+  You can change which and how many users are seeded for a feature dynamically by
+  updating the database via the Sapling API. Core features are the ability to seed
+  a feature for specific users and/or a percentage of users.
+email:
 - shanebdavis@imikimi.com
 - jason@cumuluscode.com
 executables: []
-
 extensions: []
-
 extra_rdoc_files: []
-
-files: 
+files:
 - .gitignore
 - Gemfile
 - README.md
@@ -202,41 +173,32 @@ files:
 - spec/sapling_examples.rb
 - spec/spec.opts
 - spec/spec_helper.rb
-has_rdoc: true
 homepage: https://github.com/imikimi/sapling
 licenses: []
-
 post_install_message: 
 rdoc_options: []
-
-require_paths: 
+require_paths:
 - lib
-required_ruby_version: !ruby/object:Gem::Requirement 
+required_ruby_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      hash: 3
-      segments: 
-      - 0
-      version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      hash: 3
-      segments: 
-      - 0
-      version: "0"
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-
 rubyforge_project: sapling
-rubygems_version: 1.5.3
+rubygems_version: 1.8.6
 signing_key: 
 specification_version: 3
-summary: Incrementally roll out your features. Uses ActiveRecord to store configuration and supports client-side roll-out of cached pages.
-test_files: 
+summary: Incrementally roll out your features. Uses ActiveRecord to store configuration
+  and supports client-side roll-out of cached pages.
+test_files:
 - spec/active_record_spec.rb
 - spec/feature_spec.rb
 - spec/javascript_generator_spec.rb