10 lines
919 B
Markdown
10 lines
919 B
Markdown
# Feature Flags Module
|
|
|
|
- **No caching.** Every `isFlagEnabled()` and `hasAccess()` call hits the database directly.
|
|
- `isFlagEnabled(flagName)` checks global on/off state. `hasAccess(flagName, context)` checks both global state AND per-entity access records (guild, user, or role).
|
|
- Access logic: flag must be globally enabled AND user must have an explicit access grant. Grants can target guildId, userId, or roleId independently.
|
|
- Commands declare `beta: true` and optionally `featureFlag: string` in the Command interface. `CommandHandler` intercepts beta commands and calls `hasAccess()` before execution.
|
|
- If a command has no explicit `featureFlag`, the command name (`interaction.commandName`) is used as the flag name fallback.
|
|
- Flag names are case-sensitive. Convention is snake_case or camelCase — no enforcement.
|
|
- Admin management via `/featureflags` command: CRUD on flags and access grants/revokes.
|