feat: Feature Flags

[dotneB]

• Support for Vercel Edge Config can be enabled if Environment Variable EDGE_CONFIG is present
  • Fallbacks to using environment variable when nothing is found in Edge Config
• Support for loading from environment variables

Note: Variables are prefixed by FEATURE_FLAGS_ (ex: FEATURE_FLAGS_MAINTENANCE_MODE) See #10

[vercel[bot]]

@dotneB is attempting to deploy a commit to the therun Team on Vercel.

A member of the Team first needs to authorize it.

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
therun-fr	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 17, 2023 4:43am

[therungg]

Should the EDGE_CONFIG be set in the default .env, or should it only exist in PROD?

I would prefer having all possible env variables in the default .env, to avoid confusion. If it shouldn't be used in local, it should have a value that indicates that, but still be present imo.

[dotneB]

Should the EDGE_CONFIG be set in the default .env, or should it only exist in PROD?

I would prefer having all possible env variables in the default .env, to avoid confusion. If it shouldn't be used in local, it should have a value that indicates that, but still be present imo.

There are limits/cost to having Edge Configs on vercel, so that's the only reason why I could see not wanting to expose it to local. Because of the number of refreshes and tests we do. And since there are limits and cost, I prefer assuming this doesn't need to be activated to function, that's why it falls back to using Env variables.

But I added it to the default .env and handle the case where it's an empty string as disabled.

[therungg]

Merged, thanks so much, @dotneB!