Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show the two different ways to use multiple Enums to define the Feature Toggles in the documentation #946

Open
litesoft opened this issue Feb 24, 2023 · 0 comments

Comments

@litesoft
Copy link

litesoft commented Feb 24, 2023

The goal is to "show" the Feature Toggles in multiple Enums, based on any or all of the following:

  • Dynamism,
  • Longevity,
  • Ownership, &/
  • Type (Experiment, Releases Sunsetting, Permissioning, and the 3 DevOps sub-types).

e.g. since Experiment(s) are ultimately owned by Product, have high Dynamism, and hopefully short Longevity; they would be grouped together in an "Experiment" enum (note: the Ownership will actually move from the Devs, thru QA, to Product, and may move backwards a few times).

@litesoft litesoft changed the title Support multiple Enums "classes" to define the Feature Toggles Show the two different ways to use multiple Enums "classes" to define the Feature Toggles Feb 24, 2023
@litesoft litesoft changed the title Show the two different ways to use multiple Enums "classes" to define the Feature Toggles Show the two different ways to use multiple Enums to define the Feature Toggles Feb 24, 2023
@litesoft litesoft changed the title Show the two different ways to use multiple Enums to define the Feature Toggles Show the two different ways to use multiple Enums to define the Feature Toggles in the documentation Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant