Feature Toggle Design Patterns for Front-End Development in Typescript
Feature toggles have many uses including hiding unfinished work, performing A/B testing and more. One of the most valuable benefits of feature toggles is that it enables Continuous Delivery and Trunk-Based Development, where code is merged into trunk without the use of long-lived feature branches and then shipped safely to production. Feature toggles allow us to differentiate between a deployment and release, the former shipping hidden code to production with no impact to end users, and the latter making those features available to users.
The techniques to implement feature toggles on the server side are fairly well-known with good library support out there. On the front-end side I’ve observed a tendency to splash if/else statements across the codebase to implement them, resulting in high technical debt and hard to maintain code. The same principles and design patterns that apply in a language like Java also apply in Typescript.
I’ve compiled five design patterns which can be used to implement feature toggles in Angular. The complete source code is here - the README.md also includes uses cases when one may want to use a particular pattern. A brief summary is below:
An attribute directive which hides content in a template based on a feature flag.
A route guard which implements the
CanActivateinterface to turn a route on/off based on a feature flag.
A dynamic component loader which loads a particular component based on a feature flag.
Selecting the right
classto use inside a component when executing business logic (based on a feature flag).
Select the right method to invoke by delegating feature decision query logic to a separate class.