-
-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update feature-flag-best-practices.md #7801
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@riboflavin is attempting to deploy a commit to the unleash-team Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @riboflavin this looks generally good. I would like to add the images back and to fix the suggestions that I have made. Once you do that, you can resubmit the PR for approval.
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
|
||
A large-scale feature flag system that enables runtime control should have at minimum the following components: | ||
* [11\. Enable traceability. Make it easy to understand flag evaluation.](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices\#11-enable-traceability-make-it-easy-to-understand-flag-evaluation) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This anchor text is not being rendered. All the other ones are though
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more suggestions.
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
|
||
**5. Continuously Updated**: Implement update mechanisms in your application so that changes to feature flag configurations are reflected without requiring application restarts or redeployments. The SDK should handle subscriptions or polling to the feature flag service for updates. | ||
5\. Continuously Updated: Implement update mechanisms in your application so that changes to feature flag configurations can be made without requiring application restarts or redeployments. The SDK should handle subscriptions or polling to the feature flag service for updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A large-scale feature flag system that enables runtime control should have at minimum the following components:
I think number 5 is not really a component per se. I can also look into this in a separate PR.
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Melinda Fekete <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Co-authored-by: Michael Ferranti <[email protected]>
Superseded by #7907 |
Updates to the Best Practices pages.