obytes / ob-dj-feature-flags Goto Github PK

frontend and mobile projects can also take advantage of implementing features flags on their side by requesting the list of feature flags from a backend endpoint (can use a custom hook to implement the same functionality)

sometimes you'd disable a feature flag from Django admin which then disables the flagged feature on the server but if your client apps still hold the old state it can cause confusion among your users since the feature will still be active on their side while the functionality would not ... it might be better if we can broadcast feature flags changes to client apps using a channel then on the client apps whenever we get a new event we update the state in the background so that whenever we get a fag check we can then access the local updated state and keep everything in sync

https://github.com/obytes/ob-dj-feature-flags/blob/c86694a317a54bd3c7d1ec35be8f305bdfc33f15/ob_dj_feature_flags/utils/decorators.py#L24C1-L28

turn on and off features based on the current environment (example: x_featue_flag only active in QA and not in PROD)