this_feature 0.6.0 → 0.6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 969159045580ea9f6117ccef0054dc95c9cd2e2d93e96d607cff03721ee017ea
-  data.tar.gz: 912ad44c5f32cdf932cae4b914fed37df1ae6f496c557f03594a15b7b77b74ac
+  metadata.gz: 03e205e9b9a6a53ff76d8c93b315eb7e8cd2f05a96a9e7f4ae9ac434371155e9
+  data.tar.gz: 1e5e996c866d55076f205a47685e295e4b04f0373aa545d183c0192d640ac8a0
 SHA512:
-  metadata.gz: e3541f52fd4314a25583f611b6cd33be4e6d9fd4e948e8dc0c0fc4158f8355a0d712bf8c5d4c6e840e6e53ffa904a4d0feb6f54e56d26546c26a9dcf2f77e1ef
-  data.tar.gz: d1b0ad6542b7971cfaae7b56047df473fa0ea5ece1793fa15f132f8a582e0b1b1d59ffe9949b213c5a8b8dd6a870f0e8f2c0e005c954c74ac5121366e209aee7
+  metadata.gz: 4ea504d76f8f435166ba50bb4643065030e40ea44626ffd4222fe60a5f80588d3242fe89dc339b14cce7b8cc1657fef016c9c59e5decdc9879f3bf64f23581b5
+  data.tar.gz: 523abe2a99278d2c559931e3b89ba0a946ca03f5e7a3fc92fd0e060555d0a0b25308d863f57904f4f4cc9ddb5fd93535e79bcee9164cff769b3d2ee61a6fcf0c

data/Gemfile.lock

@@ -1,32 +1,32 @@
 PATH
   remote: .
   specs:
-    this_feature (0.6.0)
-    this_feature-adapters-flipper (0.6.0)
+    this_feature (0.6.1)
+    this_feature-adapters-flipper (0.6.1)
       flipper (~> 0.16)
       flipper-active_record (~> 0.16)
       this_feature
-    this_feature-adapters-split_io (0.6.0)
+    this_feature-adapters-split_io (0.6.1)
       splitclient-rb
       this_feature
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activemodel (6.0.3.2)
-      activesupport (= 6.0.3.2)
-    activerecord (6.0.3.2)
-      activemodel (= 6.0.3.2)
-      activesupport (= 6.0.3.2)
-    activesupport (6.0.3.2)
+    activemodel (6.1.3)
+      activesupport (= 6.1.3)
+    activerecord (6.1.3)
+      activemodel (= 6.1.3)
+      activesupport (= 6.1.3)
+    activesupport (6.1.3)
       concurrent-ruby (~> 1.0, >= 1.0.2)
-      i18n (>= 0.7, < 2)
-      minitest (~> 5.1)
-      tzinfo (~> 1.1)
-      zeitwerk (~> 2.2, >= 2.2.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+      zeitwerk (~> 2.3)
     byebug (11.1.2)
     coderay (1.1.2)
-    concurrent-ruby (1.1.6)
+    concurrent-ruby (1.1.8)
     connection_pool (2.2.3)
     database_cleaner (1.8.4)
     database_cleaner-active_record (1.8.0)
@@ -44,13 +44,13 @@ GEM
       flipper (~> 0.20.3)
     gem-release (2.2.1)
     hitimes (1.3.1)
-    i18n (1.8.5)
+    i18n (1.8.9)
       concurrent-ruby (~> 1.0)
     json (2.5.1)
     jwt (2.2.2)
     lru_redux (1.1.0)
     method_source (1.0.0)
-    minitest (5.14.1)
+    minitest (5.14.4)
     multipart-post (2.1.1)
     net-http-persistent (4.0.1)
       connection_pool (~> 2.2)
@@ -78,7 +78,7 @@ GEM
     ruby2_keywords (0.0.4)
     socketry (0.5.1)
       hitimes (~> 1.2)
-    splitclient-rb (7.2.2)
+    splitclient-rb (7.2.3)
       concurrent-ruby (~> 1.0)
       faraday (>= 0.8)
       json (>= 1.8)
@@ -90,9 +90,9 @@ GEM
       thread_safe (>= 0.3)
     sqlite3 (1.4.2)
     thread_safe (0.3.6)
-    tzinfo (1.2.7)
-      thread_safe (~> 0.1)
-    zeitwerk (2.4.0)
+    tzinfo (2.0.4)
+      concurrent-ruby (~> 1.0)
+    zeitwerk (2.4.2)
 
 PLATFORMS
   ruby

data/docs/memory.md

@@ -4,7 +4,7 @@
 
 Under the hood, the memory adapter stores data in a dictionary like so:
 
-```json
+```ruby
 {
   some_flag_name: {
     global: false,
@@ -41,7 +41,7 @@ ThisFeature.configure do |config|
 end
 ```
 
-The initializer takes an optional `context_key_method` argument. This is only relevant when using `context` - 
+The initializer takes an optional `context_key_method` argument. This is only relevant when using `context` -
 it specifies a method name which should be called on the context object to determine its identity.
 For example:
 
@@ -66,19 +66,11 @@ If this option is ommitted, then the context object uses its `self` as its "iden
 
 The Memory adapter supports the public API of `ThisFeature`.
 
-The `context` argument is supported, but not `data`.
-
-Read the following notes as well:
+### **#on? / #off?**
 
-- **on?** / **off?**: If passed a `context` argument, uses the aformentioned logic
+If passed a `context` argument, uses the aformentioned logic
 (`context_key_method`) to determine how it's handled.
 
-- **control?** is not yet implemented
-
-We also support two additional methods here that aren't present on the main adapter yet:
-
-- **on!** / **off!**
-
 Usage example of these:
 
 ```ruby
@@ -86,3 +78,11 @@ Usage example of these:
 ThisFeature.test_adapter.on!(:flag_name, context: user) # with context
 ThisFeature.test_adapter.off!(:flag_name)               # without context
 ```
+
+### **#clear**
+
+Since the memory adapter stores flags in memory, it won't automatically get cleaned up in your tests. You can use this method to reset the memory adapter state.
+
+```ruby
+ThisFeature.test_adapter.clear
+```

data/lib/this_feature/adapters/memory.rb

@@ -31,6 +31,10 @@ class ThisFeature
         !on?(flag_name, context: context, data: data)
       end
 
+      def control?(flag_name, **kwargs)
+        !present?(flag_name)
+      end
+
       def on!(flag_name, context: nil, data: {})
         storage[flag_name] ||= {}
 

data/lib/this_feature/version.rb

@@ -1,3 +1,3 @@
 class ThisFeature
-  VERSION = "0.6.0"
+  VERSION = "0.6.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: this_feature
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.6.1
 platform: ruby
 authors:
 - Max Pleaner
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-02-24 00:00:00.000000000 Z
+date: 2021-03-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler