by victor_e on 4/4/22, 12:38 AM with 5 comments
by dabeeeenster on 4/4/22, 10:35 AM
[1] https://docs.flagsmith.com/guides-and-examples/mobile-app-ve...
[2] https://docs.flagsmith.com/guides-and-examples/staged-featur...
[3] https://docs.flagsmith.com/guides-and-examples/testing-push-...
by jaredsohn on 4/4/22, 10:22 AM
You can also create features that apply to individual users or if enterprise then to all users in the customer. This can be done by creating some boolean fields in the database (using a single feature_flags json field is recommended because then you don't have to change the schema every time a new feature flag is added.)
And then in code you check against the environment variable or against the user / customer before running changed functionality via a simple if statement.
by swah on 4/4/22, 11:12 AM
For example, I have some projects using using redux-saga, I'll do something like:
if (env.EnableSomeNewThing) {
yield fork(saga1)
}
So this behavior can be enabled/disabled using an env variable instead of commenting/reverting code from Git. Of course this could also be more sophisticated: enable via configuration, enable for a sample of the users, or premium users...by efortis on 4/4/22, 1:44 AM
if (hasFeatureX) doX()
else …
If it has to be more complex than that, I use a feature branch.by Valord on 4/4/22, 4:27 AM