-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
feature(gatsby): Enable partial releases of flags to a % of users #28387
Conversation
@@ -17,8 +42,17 @@ export interface IFlag { | |||
// resolved and ~50+ people have tested it, experimental should be set to | |||
// false. | |||
experimental: boolean | |||
// Generally just return true. |
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.
how the testFitness
function works
|
||
if (optedInFlags.size > 0) { | ||
message += `\n` | ||
message += `We're shipping new features! For final testing, we're rolling them out first to a small % of Gatsby users |
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.
message when we opt a site in
lodash: `>=4.9`, | ||
} | ||
if ( | ||
satisfiesSemvers(semver) && |
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.
how semver filtering would work — in a real flag, we'd generally also return true
if it passes semver but doesn't pass the opt-in
Is it possible to let ssr use the same hot-module-overlay and fast-refresh overlay when an error occurs instead of doing our own? |
Is it possible to output enabled flags in |
da5b4e8
to
09ea3b4
Compare
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.
Let's merge it!
…tsbyjs#28387) * feature(gatsby): Enable partial releases of flags to a % of users * switch to a general 'testFitness' function for one-off checks on flags * typescripting * cleanup comment * Add FAST_REFRESH * Opt-in QoD & LazyImages for ~10% of users * update snapshot for newline * includePrelease for semver checks * no double isCI in IFlag interface * type unknownConfigFlags array * don't treat unfit flags are unknown * Update packages/gatsby/src/utils/flags.ts * fix lint Co-authored-by: Michal Piechowiak <[email protected]>
We'll start with rolling out QUERY_ON_DEMAND & LAZY_IMAGES to 10% of users.
A user can opt out of the roll-out by setting the flag to false in their gatsby-config.js.