-
Notifications
You must be signed in to change notification settings - Fork 446
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
chore(): add disclaimer for boostrapping feature flags behavior post-init #9988
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Looks good, some minor style comments :)
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.
stamped from a "this is how flags work" standpoint
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
Changes
I received a ticket this week where a user was expecting feature flag bootstrapping to override flag values even after initialization. While looking into their question I came across a few other tickets around the same confusion from the last few months. Adding a couple of blurbs to the bootstrapping documentation to clear up this behavior and suggest proper overrides if that is what is desired.
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.json
Useful resources