We currently show in-progress features for the stage-beta environment only. We do this by wrapping code in a function, named isBetaFeature. Unfortunately, it can be difficult to distinguish code segments belonging to a specific feature. Instead, it would be preferable to create a new isFeatureVisible function that allows features to be named.

This would help identify multiple code segments belonging to any given feature. That is, when it comes time to enable the feature in other environments; stage-stable, prod-beta, etc. We could then search the code for the FeatureType.currency tag; for example, to see all the wrapped code for just the currency feature. This would be easier to read because features like "GCP filtered by OpenShift", "async exports", IBM, etc. would be omitted.