flipper 0.16.0 → 0.16.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 49607173763cd256cdb8f6a9ef1ada1fb213092a
-  data.tar.gz: 123bcd59f941d0a4673526132bab358c75ada4ae
+  metadata.gz: 0d3f43b874f8dfd5484317d635fd96662f8c4aab
+  data.tar.gz: 83b68438215b14a9f1fd6ba0782ceaa87f08e592
 SHA512:
-  metadata.gz: bf6951c97102685c5222c8b096133857b0a7a3251190cd3e6cf8885b0260463c341b8bb9f02e100e2ea2f541999ff6c7c53e6d4f73abed1cea09c8327f70acd4
-  data.tar.gz: 10ecb72720e4b8a58956d025351118810baa6c20c82ec629ea6c5117b870cf2ef499958ba6efd6e924ecfadc86776a73be66a11c200251e39d08c64897452c72
+  metadata.gz: 8d05d3d79dbe8150d0e7cda538f9cb891d7e05ad04faf9fb55ef10cf693406bdc8d84783cb70bdfccecbfdbeb6b5569df54b3742bb13108a35fa04a201872776
+  data.tar.gz: 11beea578344f06abd0e203e92b8eda7277ee8ac556adab9f756af0745e926059510a0063ff13f121edde890af7ea9b8b38e367ddc31c73c8646d28d36b72b19

data/Changelog.md

@@ -1,3 +1,13 @@
+## 0.16.1
+
+### Additions/Changes
+
+* Add actors API endpoint (https://github.com/jnunemaker/flipper/pull/372).
+* Fix rack body proxy require for those using flipper without rack  (https://github.com/jnunemaker/flipper/pull/376).
+* Unescapes feature_name in FeatureNameFromRoute (https://github.com/jnunemaker/flipper/pull/377).
+* Replace delete_all with destroy_all in ActiveRecord adapter (https://github.com/jnunemaker/flipper/pull/395)
+* Target correct bootstrap breakpoints in flipper UI (https://github.com/jnunemaker/flipper/pull/396)
+
 ## 0.16.0
 
 ### Bug Fixes

data/docs/Gates.md

@@ -13,69 +13,7 @@ flipper[:stats].disable # turn off
 flipper[:stats].enabled? # check
 ```
 
-## 2. Group
-
-Turn on feature based on the return value of block. Super flexible way to turn on a feature for multiple things (users, people, accounts, etc.) as long as the thing returns true when passed to the block.
-
-```ruby
-# this registers a group
-Flipper.register(:admins) do |actor|
-  actor.respond_to?(:admin?) && actor.admin?
-end
-
-flipper = Flipper.new(adapter)
-
-flipper[:stats].enable flipper.group(:admins) # This registers a stats feature and turns it on for admins (which is anything that returns true from the registered block).
-flipper[:stats].disable flipper.group(:admins) # turn off the stats feature for admins
-
-person = Person.find(params[:id])
-flipper[:stats].enabled? person # check if enabled, returns true if person.admin? is true
-
-# you can also use shortcut methods. This also registers a stats feature and turns it on for admins.
-flipper.enable_group :stats, :admins
-person = Person.find(params[:id])
-flipper[:stats].enabled? person # same as above. check if enabled, returns true if person.admin? is true
-
-flipper.disable_group :stats, :admins
-flipper[:stats].enable_group :admins
-flipper[:stats].disable_group :admins
-```
-
-Here's a quick explanation of the above code block:
-
-```
-Flipper.register(:admins) do |actor|
-  actor.respond_to?(:admin?) && actor.admin?
-end
-```
-- The above first registers a group called `admins` which essentially saves a [Proc](http://www.eriktrautman.com/posts/ruby-explained-blocks-procs-and-lambdas-aka-closures) to be called later.
-
-```
-flipper[:stats].enable flipper.group(:admins)
-```
-
-- The above enables the stats feature to any object that returns true from the `:admins` proc.
-
-```
-person = Person.find(params[:id])
-flipper[:stats].enabled? person # check if person is enabled, returns true if person.admin? is true
-```
-
-When the `person` object is passed to the `enabled?` method, it is then passed into the proc. If the proc returns true, the entire statement returns true and so `flipper[:stats].enabled? person` returns true. Whatever logic follows this conditional check is then executed.
-
-There is no requirement that the thing yielded to the block be a user model or whatever. It can be anything you want, therefore it is a good idea to check that the thing passed into the group block actually responds to what you are trying to do in the `register` proc.
-
-In your application code, you can do something like this now:
-
-```
-if flipper[:stats].enabled?(some_admin)
-  # do thing...
-else
-  # do not do thing
-end
-```
-
-## 3. Individual Actor
+## 2. Individual Actor
 
 Turn feature on for individual thing. Think enable feature for someone to test or for a buddy. The only requirement for an individual actor is that it must respond to `flipper_id`.
 
@@ -117,7 +55,7 @@ class Group
 end
 ```
 
-## 4. Percentage of Actors
+## 3. Percentage of Actors
 
 Turn this on for a percentage of actors (think user, member, account, group, whatever). Consistently on or off for this user as long as percentage increases. Think slow rollout of a new feature to a percentage of things.
 
@@ -141,7 +79,7 @@ flipper[:search].enable_percentage_of_actors 10
 flipper[:search].disable_percentage_of_actors # sets to 0
 ```
 
-## 5. Percentage of Time
+## 4. Percentage of Time
 
 Turn this on for a percentage of time. Think load testing new features behind the scenes and such.
 
@@ -165,3 +103,65 @@ flipper[:search].disable_percentage_of_time # sets to 0
 ```
 
 Timeness is not a good idea for enabling new features in the UI. Most of the time you want a feature on or off for a user, but there are definitely times when I have found percentage of time to be very useful.
+
+## 5. Group
+
+Turn on feature based on the return value of block. Super flexible way to turn on a feature for multiple things (users, people, accounts, etc.) as long as the thing returns true when passed to the block.
+
+```ruby
+# this registers a group
+Flipper.register(:admins) do |actor|
+  actor.respond_to?(:admin?) && actor.admin?
+end
+
+flipper = Flipper.new(adapter)
+
+flipper[:stats].enable flipper.group(:admins) # This registers a stats feature and turns it on for admins (which is anything that returns true from the registered block).
+flipper[:stats].disable flipper.group(:admins) # turn off the stats feature for admins
+
+person = Person.find(params[:id])
+flipper[:stats].enabled? person # check if enabled, returns true if person.admin? is true
+
+# you can also use shortcut methods. This also registers a stats feature and turns it on for admins.
+flipper.enable_group :stats, :admins
+person = Person.find(params[:id])
+flipper[:stats].enabled? person # same as above. check if enabled, returns true if person.admin? is true
+
+flipper.disable_group :stats, :admins
+flipper[:stats].enable_group :admins
+flipper[:stats].disable_group :admins
+```
+
+Here's a quick explanation of the above code block:
+
+```
+Flipper.register(:admins) do |actor|
+  actor.respond_to?(:admin?) && actor.admin?
+end
+```
+- The above first registers a group called `admins` which essentially saves a [Proc](http://www.eriktrautman.com/posts/ruby-explained-blocks-procs-and-lambdas-aka-closures) to be called later.
+
+```
+flipper[:stats].enable flipper.group(:admins)
+```
+
+- The above enables the stats feature to any object that returns true from the `:admins` proc.
+
+```
+person = Person.find(params[:id])
+flipper[:stats].enabled? person # check if person is enabled, returns true if person.admin? is true
+```
+
+When the `person` object is passed to the `enabled?` method, it is then passed into the proc. If the proc returns true, the entire statement returns true and so `flipper[:stats].enabled? person` returns true. Whatever logic follows this conditional check is then executed.
+
+There is no requirement that the thing yielded to the block be a user model or whatever. It can be anything you want, therefore it is a good idea to check that the thing passed into the group block actually responds to what you are trying to do in the `register` proc.
+
+In your application code, you can do something like this now:
+
+```
+if flipper[:stats].enabled?(some_admin)
+  # do thing...
+else
+  # do not do thing
+end
+```

data/docs/api/README.md

@@ -815,6 +815,41 @@ Successful disabling of a percentage of time will set the percentage to 0 and re
 }
 ```
 
+### Check if features are enabled for an actor
+
+**URL**
+
+`GET /actors/{flipper_id}`
+
+**Parameters**
+
+* `keys` - comma-separated list of features to check
+
+**Request**
+
+```
+curl -X GET http://example.com/flipper/api/actors/user:1?keys=my_feature_1,my_feature_2
+```
+
+**Response**
+
+Returns whether the actor with the provided flipper_id is enabled for the specififed feature keys.
+If no keys are specified all features are returned.
+
+```json
+{
+  "flipper_id": "user:1",
+    "features": {
+      "my_feature_1": {
+        "enabled": true,
+      },
+      "my_feature_2": {
+        "enabled": false,
+      }
+    }
+}
+```
+
 ## Errors
 In the event of an error the Flipper API will return an error object.  The error object will contain a Flipper-specific error code, an error message, and a link to documentation providing more information about the error.
 

data/lib/flipper/middleware/memoizer.rb

@@ -1,5 +1,3 @@
-require 'rack/body_proxy'
-
 module Flipper
   module Middleware
     class Memoizer

data/lib/flipper/version.rb

@@ -1,3 +1,3 @@
 module Flipper
-  VERSION = '0.16.0'.freeze
+  VERSION = '0.16.1'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: flipper
 version: !ruby/object:Gem::Version
-  version: 0.16.0
+  version: 0.16.1
 platform: ruby
 authors:
 - John Nunemaker
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-08-01 00:00:00.000000000 Z
+date: 2019-02-05 00:00:00.000000000 Z
 dependencies: []
 description: Feature flipper is the act of enabling/disabling features in your application,
   ideally without re-deploying or changing anything in your code base. Flipper makes