Add feature flag docs#9127
Conversation
MobileInstall the Dev Tool (iOS via TestFlight, iOS Simulator, or Android .apk) here. Scan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client.
Deep linksiOS Android Web (Vercel)View the Vercel web preview for this branch. Backend
Other
|
|
@aapeliv This is a great start! One thing that would be super helpful is to add examples of the flags in use for frontend and backend to the doc. Maybe we could copy/paste some existing code blocks where the different types of flags are being used? |
|
When do I use |
|
Can you add some info for how to make a feature across frontend and backend visible on dev and staging but not prod? |
|
Maybe some info about how to use this in the dev flow, i.e. do we need to manually switch the feature flags on when we code to see the feature while it's in progress? |
f8c08fd to
49a2277
Compare
|
|
||
| The local backend does not pull the feature flags from the server, instead it resolves them from the override file in `feature-flags.dev.json`. You should set a value here that makes sense for devs developing locally (e.g. enable experimental features), and you can use it for local debug/testing temporary overrides (but don't commit this). | ||
|
|
||
| TODO: there is currently no such mechanism in the frontend; you can just manually modify the place where you check the flags. |
There was a problem hiding this comment.
Let's move this right to the top so it's obvious no frontend for now?
|
|
||
| ## Setting the value of a feature flag to a non-default value | ||
|
|
||
| To set the value of a feature flag to a non-default value for everyone for a given environment, follow this process: |
There was a problem hiding this comment.
It's not super clear to me what this means and when we would want to do it?
3 participants
No description provided.