feat(web): restructure feature flags vs remote config - Githubissues

tryabby / abby

Open-Source Feature Flags, Remote Config & A/B Tests for Developers ⛳🧪

https://www.tryabby.com

GNU Affero General Public License v3.0

143 stars 19 forks source link

feat(web): restructure feature flags vs remote config #62

Closed cstrnt closed 1 year ago

cstrnt commented 1 year ago

Create a new menu entry for remote config
Move all non-boolean flags in the UI there
Move A/B tests down in menu hierarchy

Questions:

Should we add the remoteConfig option to the A/BBY config in the code as well?
Should we add a new hook useRemoteConfig? (and the same for angular)

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
abby-opensource	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2023 9:00am

1 Ignored Deployment

| Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **abby-docs** | ⬜️ Ignored ([Inspect](https://vercel.com/dynabase/abby-docs/4yd6Nbi6rnairQCJkU5uJwLGfHT4)) | [Visit Preview](https://abby-docs-git-feat-restructurefeatureflagsvsrem-1510d1-dynabase.vercel.app) | | Sep 10, 2023 9:00am |

CakeWithDivinity commented 1 year ago

Feature flags are now split into feature flags and remote config for the core and angular package. Next steps:

Return values for remoteConfig in REST and TRPC Api
Adapt svelte, react and next packages to changes in the core