Feat: config env route

[HugoPerard]

Add a new server route to expose env config info

Summary by CodeRabbit

• New Features
  • New configuration endpoint now available for retrieving environment-specific application settings, including display properties (name, color, emoji) and environment state indicators.

[coderabbitai]

Walkthrough

A new configuration router is introduced that exposes environment configuration values via a GET /config/env endpoint. The router is imported and integrated into the main router object, extending the public API surface with config-related endpoints.

Changes

Cohort / File(s)	Summary
Router integration src/server/router.ts	Added import for configRouter and extended the router object with a new top-level config property referencing configRouter
Config router endpoint src/server/routers/config.ts	New file defining a config router with a public GET /config/env procedure that returns environment configuration (name, color, emoji, isDemo) and a runtime DEV flag with zod schema validation

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "Feat: config env route" directly and clearly describes the main change in the changeset. The changes add a new server router file that exposes a GET /config/env endpoint and integrate it into the main router structure. The title is specific, concise, and uses descriptive terms ("config env route") that accurately reflect the purpose of the changes. A teammate reviewing the repository history would clearly understand that this pull request introduces a new feature for accessing config environment information through an API route.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/config-env-route

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

src/server/routers/config.ts (4)

6-6: Make tags readonly.

Minor type-safety/readability improvement; prevents accidental mutation and preserves tuple literal types.

-const tags = ['config'];
+const tags = ['config'] as const;

---

11-18: Optionally centralize the schema for reuse (server/client).

Export a named EnvConfigSchema and reference it in output; makes typing reusable for clients and tests.

 import { publicProcedure } from '@/server/orpc';

-const tags = ['config'];
+const tags = ['config'] as const;
+
+export const EnvConfigSchema = z.object({
+  name: z.string().min(1).optional(),
+  color: z.string(),
+  emoji: z.string().min(1).optional(),
+  isDemo: z.boolean(),
+  isDev: z.boolean(),
+});

 export default {
   env: publicProcedure()
     .route({ method: 'GET', path: '/config/env', tags })
-    .output(
-      z.object({
-        name: z.string().optional(),
-        color: z.string(),
-        emoji: z.string().optional(),
-        isDemo: z.boolean(),
-        isDev: z.boolean(),
-      })
-    )
+    .output(EnvConfigSchema)

---

20-28: Confirm server runtime for import.meta.env.DEV; consider sourcing from the same env helper.

If this code ever runs outside Vite’s transform (e.g., ts-node/tests), import.meta.env may be undefined. For consistency with envClient, consider reusing the same isDev source you already rely on there.

Example (only if available in your env helpers):

-        isDev: import.meta.env.DEV,
+        isDev: envClient.__IS_DEV__ ?? import.meta.env.DEV,

Or inject a small util exporting isDev used across server and env parsing.

---

8-29: Optional: add caching hint/metadata.

Values are static per build/env; if your framework supports per-route cache metadata or headers, set a reasonable max-age (e.g., 5–15 minutes) to cut noise.

Happy to wire this if you share the caching API used with orpc/your server.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d060dd1 and 5f99d61.

📒 Files selected for processing (2)

• src/server/router.ts (2 hunks)
• src/server/routers/config.ts (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

src/server/routers/config.ts (1)

src/env/client.ts (1)

• envClient (24-52)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: 🔬 Tests (24)
• GitHub Check: 🔬 Tests (lts/*)
• GitHub Check: Playwright E2E Tests
• GitHub Check: 🔬 Tests (22)

🔇 Additional comments (2)

src/server/router.ts (1)

5-5: LGTM; route mounted correctly.

Import and mount look consistent with existing pattern. Ensure any generated client/types are refreshed.

Quick checklist:

• Run typegen/client generation if applicable.
• Hit GET /config/env once in dev to confirm discovery and no double-prefixing.

Also applies to: 17-17

src/server/routers/config.ts (1)

10-10: The review comment's concern is unfounded—there is no auto-prefixing.

The ORPC framework does not automatically prefix routes based on parent keys. This is evident from the codebase patterns:

• book.ts (registered as book: bookRouter) uses paths like /books and /users/{id} without /book/ prefix
• user.ts (registered as user: userRouter) uses paths like /users without /user/ prefix
• genre.ts (registered as genre: genreRouter) uses /genres without /genre/ prefix
• account.ts (registered as account: accountRouter) intentionally includes namespace: /account/submit-onboarding
• config.ts (registered as config: configRouter) follows the same pattern: /config/env

The hardcoded /config/env path is intentional and consistent with how account.ts structures its routes. The path will not become /config/config/env because no auto-prefixing occurs.

Likely an incorrect or invalid review comment.