Add a way to check feature flags with some type-safety

[ogzhanolguncu]

Preliminary Checks

• I have reviewed https://unkey.com/docs for existing features that would solve my problem

• I have searched for existing feature requests: https://github.com/unkeyed/unkey/issues

• This issue is not a question, general help request, or anything other than a feature request directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.

Is your feature request related to a problem? Please describe.

Developers need to modify the database for feature flags during local development, which creates unnecessary friction. A type-safe checkFlag function could bypass this requirement in development mode while maintaining proper flag checking in production.

Example:

  if (!workspace.betaFeatures.logsPage) {
    return notFound();
  }

Describe the solution

We could create a checkFlag function that takes two parameters: a feature flag name and a workspace object. This would provide several things:

1. Type safety - by using a type like:

type ConfigObject = Extract<typeof workspaces['betaFeatures']['default'], {
   rbac?: boolean;
   ratelimit?: boolean; 
   identities?: boolean;
   logsPage?: boolean;
}>;

2. Easy bypassing of feature flags in development:

function checkFlag<T extends keyof ConfigObject>(
    flagName: T, 
    workspace
): boolean {
    if (process.env.NODE_ENV === "development") {
        return true
    }
    // Normal flag checking logic...
}

This pattern would help ensure we're only checking for flags that actually exist in our configuration, while making it simple to enable all features in development environments.

Describe alternatives you have considered (if any)

No response

Additional context

No response

[linear]

ENG-1584 Add a way to check feature flags with some type-safety

[chronark]

bro just submit the PR instead of coding in issues :D