I plan on supporting the adapters in the flipper repo. Other adapters are welcome, so please let me know if you create one.
- memory adapter – great for tests
- PStore adapter – great for when a local file is enough
- Mongo adapter
- Redis adapter
- ActiveRecord adapter - Rails 3 and 4.
- Cassanity adapter
The basic API for an adapter is this:
features
- Get the set of known features.add(feature)
- Add a feature to the set of known features.remove(feature)
- Remove a feature from the set of known features.clear(feature)
- Clear all gate values for a feature.get(feature)
- Get all gate values for a feature.enable(feature, gate, thing)
- Enable a gate for a thing.disable(feature, gate, thing)
- Disable a gate for a thing.
If you would like to make your own adapter, there are shared adapter specs (RSpec) and tests (MiniTest) that you can use to verify that you have everything working correctly.
For example, here is what the in-memory adapter spec looks like:
spec/flipper/adapters/memory_spec.rb
require 'helper'
require 'flipper/adapters/memory'
# The shared specs are included with the flipper gem so you can use them in
# separate adapter specific gems.
require 'flipper/spec/shared_adapter_specs'
describe Flipper::Adapters::Memory do
# an instance of the new adapter you are trying to create
subject { described_class.new }
# include the shared specs that the subject must pass
it_should_behave_like 'a flipper adapter'
end
Here is what an in-memory adapter MiniTest looks like:
test/adapters/memory_test.rb
require 'test_helper'
require 'flipper/adapters/memory'
class MemoryTest < MiniTest::Test
prepend SharedAdapterTests
def setup
# Any code here will run before each test
@adapter = Flipper::Adapters::Memory.new
end
def teardown
# Any code here will run after each test
end
end
-
Create a file under
test/adapters
that inherits from MiniTest::Test. -
prepend SharedAdapterTests
. -
Initialize an instance variable
@adapter
referencing an instance of the adapter. -
Add any code to run before each test in a
setup
method and any code to run after each test in ateardown
method.
A good place to start when creating your own adapter is to copy one of the adapters mentioned above and replace the client specific code with whatever client you are attempting to adapt.
I would also recommend setting fail_fast = true
in your RSpec configuration as that will just give you one failure at a time to work through. It is also handy to have the shared adapter spec file open.