Feature management
Feature flag best practices
Short-lived gates, server keys, and explicit exposures.
لا توجد ترجمة عربية منشورة لهذه الصفحة بعد. النص الإنجليزي هو المرجع.
Last updated on
- Keep one key per behavior. Do not overload a boolean with several meanings.
- Evaluate server-only decisions with
@flagfix/nodeand aSERVER_SDKkey. - Ship the
CLIENT_SDKkey only if the flag values are safe to expose. - Call
trackExposureat the point of display, not insidehasFeature. - Publish the kill switch before you need it. A draft does nothing for SDKs.
- Roll out with a salt you can rotate if a bucket looks skewed. Rotation reassigns users.
- Remove the flag from code after the rollout is finished. The platform will not delete the call sites for you.
هل كانت هذه الصفحة مفيدة؟