Carbon: Expose feature flags as package

[SimonFinney]

Is your feature request related to a problem? Please describe.

Security is currently using a v* branching model for major releases which causes heartache depending on how long that major version is in development.

Describe the solution you'd like

Would it be possible to expose the JavaScript and Sass feature flag implementation as a package for teams to leverage the infrastructure already in use throughout Carbon?

Describe alternatives you've considered

Importing the feature flag files from carbon-components and carbon-components-react directly.

[asudoh]

Hi @SimonFinney weighing in - Given carbon-elements code has no code corresponding to Carbon v9 code (the biggest usage of Carbon feature flags is v9/v10 switch), would you want to elaborate what headache you are facing...? Thanks!

[joshblack]

@asudoh I believe the request is to extract the functionality so that they could also use feature flags in their add-on setup, not necessarily directly use our flags.

In other words, how could they use feature-flag-enabled but for their own flags for carbon-addons-security 😄

[asudoh]

Got it - The logic behind feature flags instead of feature flags themselves. Thanks @joshblack for clarifying! As @joshblack knows, we have feature flags just as a map and use a utility function (just a half-dozen lines of code) to access the map entry. That said, you can maintain your own set of feature flags, which won't be hard.

[SimonFinney]

@asudoh / @joshblack - That's right, and apologies for the confusion! We want to leverage the feature flag infrastructure that Carbon' uses to prevent us having to reimplement a separate solution ourselves.

[stale[bot]]

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. Thanks for your contributions.

[stale[bot]]

As there's been no activity since this issue was marked as stale, we are auto-closing it.

[stale[bot]]

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.

[stale[bot]]

As there's been no activity since this issue was marked as stale, we are auto-closing it.