Using flag testing within a backend API doesn't work as well when you have to trigger the flag via a query params. I believe that using HTTP headers is a more natural way of indicating these flags for an API. This PR adds support for checking headers for DWFT-Flag-Name to enable/disable the flag the same as using the query params. This shouldn't affect the existing functionality, simply make Waffle more flexible for additional use cases.
Using flag testing within a backend API doesn't work as well when you have to trigger the flag via a query params. I believe that using HTTP headers is a more natural way of indicating these flags for an API. This PR adds support for checking headers for
DWFT-Flag-Name
to enable/disable the flag the same as using the query params. This shouldn't affect the existing functionality, simply make Waffle more flexible for additional use cases.