fix: restore accidentally deleted organizations schema tables

[anshul23102]

User description

Restores the multi-tenant organizations schema tables that were accidentally deleted in PR #731.

Changes

• Restore orgRoleEnum, organizationsTable, organizationMembershipsTable
• Restore organizationId column in classroomsTable with FK
• Fixes compilation errors in organizations/route.ts, rooms/route.ts, analytics/route.ts

Closes #777

Summary by CodeRabbit

• New Features
  • Added support for organizations and organization-based roles.
  • Classrooms can now be linked to an organization, with organization links safely cleared if the organization is removed.
  • Added support for tracking memberships between users and organizations.

---

CodeAnt-AI Description

Fix route errors and keep the test suite aligned with current responses

What Changed

• Teacher insights now returns the current error messages for an invalid classroom ID and denied access
• Digest-related tests now match the way digest emails and Inngest functions behave, so the suite runs without breaking on mocks
• A few route/database type issues were cleaned up so the app compiles without unnecessary failures
• Old migration files were removed from the tracked set

Impact

✅ Fewer failing test runs
✅ Clearer teacher insights error messages
✅ Fewer build-time type errors

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[vercel]

@anshul23102 is attempting to deploy a commit to the Karan Mani Tripathi 's projects Team on Vercel.

A member of the Team first needs to authorize it.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Walkthrough

Restores multi-tenant organization schema definitions in src/configs/schema.ts, including orgRoleEnum, organizationsTable, and organizationMembershipsTable, and reintroduces a nullable organizationId column on classroomsTable with an index and foreign key referencing organizations with cascade set-null on delete.

Changes

Organizations Schema Restoration

Layer / File(s)	Summary
Organization and membership tables src/configs/schema.ts	Adds pgEnum import, orgRoleEnum, organizationsTable, and organizationMembershipsTable with role, timestamps, uniqueness constraints, and cascading foreign keys.
Classroom organization linkage src/configs/schema.ts	Adds nullable organizationId column to classroomsTable, an index on that column, and an orgIdFk foreign key to organizationsTable with onDelete("set null").

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• knoxiboy/DoubtDesk#705: Introduces the same multi-tenant organization tables and classroom foreign key that this PR restores.

Suggested reviewers: knoxiboy

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The PR restores the deleted org schema exports and classroom organizationId column required by #777.
Out of Scope Changes check	✅ Passed	The changes stay within the issue scope and only restore the missing organizations schema pieces.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: restoring the accidentally deleted organizations schema tables.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[github-actions]

@coderabbitai review

[codeant-ai]

Suggestion: organizationMembershipsTable references usersTable.email before usersTable is declared in the module, which can trigger a temporal-dead-zone initialization failure when schema metadata is built. Move usersTable above this table definition (or defer the FK target lookup in a way that is guaranteed to execute after initialization) so module load does not fail. [incorrect variable usage]

Severity Level: Critical 🚨

- ❌ All modules importing configs/schema crash at load.
- ❌ Cover letter API endpoint fails on first request.
- ❌ Classroom invite API endpoint fails due to schema error.
- ❌ Reply vote API endpoint fails importing repliesTable schema.
- ⚠️ Test suites importing schema cannot run in CI.
- ⚠️ Future org membership features unusable until fixed.

Steps of Reproduction ✅

1. Note module configuration in `tsconfig.json` at lines 2-16: target is "ES2017" and
module is "esnext", meaning TypeScript emits ES modules with `const` semantics and
temporal dead zone behavior.

2. Inspect `src/configs/schema.ts` where `organizationMembershipsTable` is defined at
lines 18-34. Its FK callback contains `userEmailFk` at lines 29-32, which builds
`foreignColumns: [usersTable.email]` while `usersTable` itself is only declared later at
lines 40-68 in the same file.

3. Observe that any import of `@/configs/schema` causes this file to be evaluated
top-to-bottom. For example, `src/lib/auth-utils.ts` at lines 1-2 imports `{ usersTable }`
from "@/configs/schema", and `src/app/api/cover-letter/route.ts` at lines 3-5 imports `{
coverLettersTable }` from "@/configs/schema", both forcing `schema.ts` to load when those
API routes are hit.

4. When the module `src/configs/schema.ts` is evaluated, the initializer for
`organizationMembershipsTable` at line 18 executes before `usersTable` is initialized at
line 40. The array literal `[usersTable.email]` in line 31 reads `usersTable` in its
temporal dead zone, causing a runtime `ReferenceError: Cannot access 'usersTable' before
initialization`, and the importing routes (e.g. `/api/cover-letter`) fail at startup or on
first request due to schema initialization crashing.

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** src/configs/schema.ts
**Line:** 29:32
**Comment:**
	*Incorrect Variable Usage: `organizationMembershipsTable` references `usersTable.email` before `usersTable` is declared in the module, which can trigger a temporal-dead-zone initialization failure when schema metadata is built. Move `usersTable` above this table definition (or defer the FK target lookup in a way that is guaranteed to execute after initialization) so module load does not fail.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[coderabbitai]

🧹 Nitpick comments (1)

src/configs/schema.ts (1)

10-16: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Consider a FK for ownerEmail.

organizationMembershipsTable.userEmail (Line 30-32) has an explicit FK to usersTable.email, but organizationsTable.ownerEmail (Line 14) does not reference usersTable at all, so orphaned/invalid owner emails aren't prevented at the DB level. Since this restores previously-deleted code, this may be pre-existing behavior rather than a regression introduced here.

♻️ Optional fix

 export const organizationsTable = pgTable("organizations", {
     id: integer().primaryKey().generatedAlwaysAsIdentity(),
     name: varchar({ length: 255 }).notNull(),
     slug: varchar({ length: 255 }).notNull().unique(),
     ownerEmail: varchar("owner_email", { length: 255 }).notNull(),
     createdAt: timestamp("created_at").defaultNow().notNull(),
-});
+}, (table) => ({
+    ownerEmailFk: foreignKey({
+        columns: [table.ownerEmail],
+        foreignColumns: [usersTable.email],
+    }),
+}));

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/configs/schema.ts` around lines 10 - 16, Add a foreign key constraint for
organizationsTable.ownerEmail so it references usersTable.email, matching the
pattern already used by organizationMembershipsTable.userEmail. Update the
organizations table definition in schema.ts to declare the relationship using
the existing table symbols (organizationsTable and usersTable) so invalid owner
emails are rejected at the database level.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/configs/schema.ts`:
- Around line 10-16: Add a foreign key constraint for
organizationsTable.ownerEmail so it references usersTable.email, matching the
pattern already used by organizationMembershipsTable.userEmail. Update the
organizations table definition in schema.ts to declare the relationship using
the existing table symbols (organizationsTable and usersTable) so invalid owner
emails are rejected at the database level.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 07e35df3-1aed-4de4-9c4d-4f7cb936008b

📥 Commits

Reviewing files that changed from the base of the PR and between 956018a and e88b416.

📒 Files selected for processing (1)

• src/configs/schema.ts

[codeant-ai]

CodeAnt AI is running Incremental review

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI Incremental review completed.

[anshul23102]

Ready for review. Clean build, all tests passing.

Quick labels when you get a sec:

• difficulty: high schema restoration with multi-tenant support
• priority: high fixes accidentally deleted tables
• GSSoC:approved for tracking
• type: fix

Thanks! 🙏

[github-actions]

This pull request has been closed because the requested features or bug fixes are already implemented in the repository.

[anshul23102]

Hey @knoxiboy! 👋

Ready for review on #784: Resolve all CI failures blocking downstream PRs (mega PR).

This is the foundational fix that unblocks 5+ stalled PRs: eliminated 100+ implicit-any TS errors across 30+ files, fixed stale test assertions, resolved drizzle migration state, and wired up the CI test suite. Every downstream PR depends on this landing first.

Suggested GSSoC labels (to help with contribution scoring):

• gssoc:approved — for GSSoC tracking
• type:ci — build/test infrastructure
• type:testing — comprehensive test fixes
• type:quality — TypeScript/linting enforcement
• type:refactoring — code quality
• priority:critical — unblocks entire queue

Infrastructure improvements that enable other PRs are high-impact! ⚙️