Feature Dependency

[azeveco]

Context

Allow defining dependencies between features (e.g., "Feature A requires Feature B"). Enabling one will auto-enable its dependencies. The other way around should also work.

Steps

• I
• Haven't
• Defined
• The
• Steps
• For
• Completion
• Yet

Expected impact

We expect to allow the release of a big feature that have a lot of small features.

Example:

• You have a big feature called checkout and this big feature uses a lot of small features, like:
  • Payment Link
  • Payment with many payment methods, like credit card, shopify, venmo
  • etc...
• If you need to enable the checkout feature to a user, then all subfeatures that depend on it will be auto-enabled
• Then later, you can customize each subfeature, like:
  • Disable a specific payment method
  • Disable a specific automation
  • etc...

References

None, that's crazy!