**Important:** the order of handlers matters! The first handler to return True stops the chain. So given the above example,if it's Tuesday, ``is_it_tuesday`` will return True and ``is_it_friday`` will not run.

You can override this behavior by raising the StopCheckingFeatureFlags exception in your custom handler:

If it isn't Tuesday, this will cause the chain to return False and any other handlers won't run.

Acknowledgements================

A big thank you to LinkedIn for letting me opensource this, and for my coworkers for all their feedback on this project. You guys are great. :)

Questions?==========

Feel free to ping me on twitter [@trustrachel](https://twitter.com/trustrachel) or on the [Github](https://github.com/trustrachel/Flask-FeatureFlags) project page.

Changes=======

0.1 (April 17, 2013)--------------------

Initial public offering.

0.2 (June 20, 2013)--------------------

Revved the version number so I could re-upload to PyPI. No real changes other than that. :/

0.3 (June 27, 2013)-------------------

* Dropped support for Python 2.5, and added support for Python 3.3 and Flask 0.10* Now testing with PyPy in Travis!* Added ``RAISE_ERROR_ON_MISSING_FEATURES`` configuration to throw an error in dev if a feature flag is missing.

0.4 (April 8, 2014)-------------------

* General code cleanup and optimization* Adding optional redirect to is_active_feature, thank you to michaelcontento * Fixed syntax error in docs, thank you to iurisilvio

0.5 (August 7, 2014)-------------------

Official support for contributed modules, thank you to iurisilvio! He contributed the first forSQLAlchemy, so you can store your flags in the database instead.

Other contributions welcome.

0.5.1 (October 13, 2014)----------------------

Adding the ability to have feature flags inline instead of in a dictionary, to make it easier to interoperate with other Flask extensions, e.g. Flask-AppConfig.