Skip to content
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

Closed
wants to merge 28 commits into from

Conversation

riboflavin
Copy link

Updates to the Best Practices pages.

Copy link

vercel bot commented Aug 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 15, 2024 6:04am
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 15, 2024 6:04am

Copy link

vercel bot commented Aug 8, 2024

@riboflavin is attempting to deploy a commit to the unleash-team Team on Vercel.

A member of the Team first needs to authorize it.

@melindafekete melindafekete requested a review from ferrantim August 9, 2024 18:36
@riboflavin riboflavin marked this pull request as ready for review August 9, 2024 19:35
Copy link
Collaborator

@ferrantim ferrantim left a 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.


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)
Copy link
Collaborator

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

Copy link
Collaborator

@melindafekete melindafekete left a 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.


**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.
Copy link
Collaborator

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.

riboflavin and others added 16 commits August 14, 2024 22:45
@melindafekete
Copy link
Collaborator

Superseded by #7907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants