feat(flags): add optional folder field (minimal schema + api support)

[agent-sure]

Closes #271 (partial, minimal first patch)

This PR adds optional folder support for flags with minimal surface area, without changing any flag evaluation logic.

What’s included

• DB schema: add folder column to flags table
• Shared validation: add optional/nullable folder in flagFormSchema
• API/router:
  • allow folder in updateFlagSchema
  • persist folder in create flow

What’s intentionally not included in this first patch

• Full folder tree UI / drag-reorder
• Dedicated folder management actions (create/rename/delete)
• Screenshot set for final UX polish

I’m using this as a safe incremental baseline and can follow up with UI organization + screenshots in next PR(s).

[vercel]

Someone is attempting to deploy a commit to the Databuddy OSS Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[dosubot]

Related Documentation

Checked 1 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds minimal folder support for feature flags by introducing an optional folder text field across the data layer, validation, and API.

Changes:

• Added nullable folder column to the flags database schema
• Added optional folder field validation (max 200 chars, alphanumeric with -_/ allowed)
• Included folder in create and update API flows

Issue Found:

• The flag restore flow (when recreating a deleted flag) is missing the folder field assignment, which means restored flags will lose their folder organization

Confidence Score: 3/5

• This PR is mostly safe but has one logical gap in the restore flow
• The implementation is clean and consistent across schema/validation/API layers, but the restore flow omits the new folder field, causing data loss when restoring deleted flags
• packages/rpc/src/routers/flags.ts needs attention for the restore flow fix

Important Files Changed

Filename	Overview
packages/db/src/drizzle/schema.ts	Added optional folder text column to flags table - clean schema change
packages/shared/src/flags/index.ts	Added optional/nullable folder field with validation (max 200 chars, alphanumeric + -_/)
packages/rpc/src/routers/flags.ts	Added folder to update schema and create flow, but missing from restore flow

Sequence Diagram

sequenceDiagram
    participant Client
    participant API
    participant Validation
    participant DB
    
    Client->>API: Create/Update Flag with folder
    API->>Validation: Validate flagFormSchema
    Validation->>Validation: Check folder regex & length
    Validation-->>API: Valid
    API->>DB: Insert/Update flags table
    Note over DB: folder column (text, nullable)
    DB-->>API: Flag with folder
    API-->>Client: Success

Loading

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

packages/rpc/src/routers/flags.ts
Missing folder field in restore flow - should add folder: input.folder here

						environment: input.environment,
						folder: input.folder,