Several project config improvements #811
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThis set of changes introduces a comprehensive refactor and extension of the configuration schema, validation, and normalization logic across the backend and shared packages. It includes stricter schema enforcement, improved type safety, new migration and sanitization utilities, expanded TypeScript type helpers, and enhanced schema introspection. Several new utility modules and functions are added for currency and date handling, and documentation is updated to clarify the config system. Minor adjustments and cleanups are made in various backend scripts and handlers to align with the new config logic. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant API_Route
participant Config_Lib
participant Schema_Utils
Client->>API_Route: PATCH /internal/email-templates/[templateId]
API_Route->>Config_Lib: overrideEnvironmentConfigOverride({ tsxSource, themeId? })
Config_Lib->>Schema_Utils: sanitizeEnvironmentConfig
Schema_Utils-->>Config_Lib: Sanitized config
Config_Lib-->>API_Route: Save override if valid
API_Route-->>Client: Response
sequenceDiagram
participant Backend
participant Config_Lib
participant Schema_Utils
Backend->>Config_Lib: validateEnvironmentConfigOverride(override)
Config_Lib->>Schema_Utils: getConfigOverrideErrors
Schema_Utils-->>Config_Lib: Result<null, string>
Config_Lib-->>Backend: Validation result
Estimated code review effort🎯 5 (Critical) | ⏱️ ~90+ minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ 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). (9)
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Greptile Summary
This PR implements a comprehensive refactor of Stack Auth's configuration management system. The changes introduce several key improvements:
Configuration System Overhaul: The core configuration system has been completely refactored with enhanced validation, migration support, and sanitization. The new system provides better error categorization (FORMAT ERROR, ERROR, WARNING) and includes comprehensive test coverage. Configuration rendering now includes normalization and sanitization steps, with migration support for backwards compatibility.
Type Safety Improvements: Significant enhancements to TypeScript utility types have been added, including better handling of union/intersection types, object manipulation utilities, and more precise type assertions. The configuration schemas now use more sophisticated typing with OptionalKeys and RequiredKeys to distinguish between required and optional fields.
Domain Storage Refactor: The trusted domains configuration has been changed from an array structure to a Map-like object structure where each domain gets a unique UUID as a key. This improves indexing, lookup performance, and follows the codebase pattern for dynamic key configurations.
Enhanced Schema Infrastructure: New schema introspection capabilities have been added through hasNested and enhanced getNested methods, along with a metadata system (stackSchemaInfo) that tracks schema types for better validation and error reporting.
Payment System Foundation: New currency handling utilities and money amount schemas have been introduced, suggesting preparation for billing/subscription features with Stripe integration.
Bug Fixes: Several critical issues were addressed, including a security vulnerability in the development key override logic and proper indentation fixes in the database seed script for GitHub OAuth account creation.
Developer Experience: Various improvements including file watching for migration imports, better error messages with deindent formatting, and more consistent import organization across the codebase.
These changes represent a significant architectural improvement that maintains the same public API while substantially enhancing the internal implementation for better reliability, type safety, and maintainability.
Confidence score: 3/5
• This PR introduces substantial architectural changes that require careful testing, particularly around the configuration validation and migration systems.
• The score reflects concerns about the complexity of the new configuration system, potential runtime issues with the date interval mutations, and incomplete currency handling implementation.
• Files needing attention: packages/stack-shared/src/utils/dates.tsx (mutation issues), packages/stack-shared/src/utils/currencies.tsx (incomplete implementation), and apps/backend/src/lib/config.tsx (complex validation logic).
21 files reviewed, 9 comments
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
packages/stack-shared/src/config/schema.ts (1)
26-31: Avoidas anycast in canNoLongerBeOverridden function.The function uses
as anycast which violates coding guidelines. Consider improving type inference to avoid this cast.
🧹 Nitpick comments (1)
packages/stack-shared/src/config/schema.ts (1)
1-1: Consider removing or addressing the TODO comment.The TODO comment suggests code quality concerns. If the code truly needs refactoring, create a proper issue to track this work rather than leaving a TODO comment.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
apps/backend/package.json(1 hunks)apps/backend/src/lib/config.tsx(15 hunks)apps/backend/src/lib/email-rendering.tsx(1 hunks)packages/stack-shared/src/config/format.ts(7 hunks)packages/stack-shared/src/config/schema.ts(4 hunks)packages/stack-shared/src/utils/strings.tsx(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- apps/backend/src/lib/email-rendering.tsx
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/stack-shared/src/utils/strings.tsx
- apps/backend/src/lib/config.tsx
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{ts,tsx}: TypeScript with strict types, prefertypeoverinterface
Avoid casting toany; Prefer making changes to the API so thatanycasts are unnecessary to access a property or method
Files:
packages/stack-shared/src/config/format.tspackages/stack-shared/src/config/schema.ts
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{js,jsx,ts,tsx}: 2-space indentation, spaces in braces, semicolons required
Return promises withreturn await, no floating promises
Proper error handling for async code with try/catch
Use helper functions:yupXyz()for validation,getPublicEnvVar()for env
Switch cases must use blocks
Files:
packages/stack-shared/src/config/format.tspackages/stack-shared/src/config/schema.ts
🧠 Learnings (3)
packages/stack-shared/src/config/format.ts (3)
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : Avoid casting to any; Prefer making changes to the API so that any casts are unnecessary to access a property or method
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Switch cases must use blocks
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use helper functions: yupXyz() for validation, getPublicEnvVar() for env
packages/stack-shared/src/config/schema.ts (3)
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use helper functions: yupXyz() for validation, getPublicEnvVar() for env
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : Avoid casting to any; Prefer making changes to the API so that any casts are unnecessary to access a property or method
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : TypeScript with strict types, prefer type over interface
apps/backend/package.json (1)
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use helper functions: yupXyz() for validation, getPublicEnvVar() for env
🧬 Code Graph Analysis (1)
packages/stack-shared/src/config/format.ts (3)
packages/stack-shared/src/utils/types.tsx (2)
OptionalKeys(44-46)RequiredKeys(47-49)packages/stack-shared/src/utils/errors.tsx (1)
StackAssertionError(67-83)packages/stack-shared/src/utils/objects.tsx (4)
set(533-535)get(537-541)hasAndNotUndefined(560-562)deleteKey(564-570)
🪛 Biome (2.1.2)
apps/backend/package.json
[error] 21-21: Missing closing quote
The closing quote must be on the same line.
(parse)
🪛 GitHub Actions: Ensure Prisma migrations are in sync with the schema
apps/backend/package.json
[error] 21-21: pnpm install failed: Bad control character in string literal in JSON at position 1545 (line 21 column 229) in package.json.
🪛 GitHub Actions: Runs E2E API Tests
apps/backend/package.json
[error] 21-21: pnpm install failed: Bad control character in string literal in JSON at position 1545 (line 21 column 229). JSON parsing error in package.json.
🪛 GitHub Actions: Dev Environment Test
apps/backend/package.json
[error] 21-21: pnpm install failed due to JSON parse error: Bad control character in string literal at position 1545 in package.json.
🪛 GitHub Actions: Runs E2E API Tests with external source of truth
apps/backend/package.json
[error] 21-21: pnpm install failed due to JSON parse error: Bad control character in string literal at position 1545.
🪛 GitHub Actions: Run setup tests
apps/backend/package.json
[error] 1-1: pnpm install failed due to JSON parse error: Bad control character in string literal in JSON at position 1545.
🪛 GitHub Actions: Lint & build
apps/backend/package.json
[error] 21-21: pnpm install failed: Bad control character in string literal in JSON at position 1545 (line 21 column 229) while parsing package.json.
⏰ 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). (3)
- GitHub Check: docker
- GitHub Check: all-good
- GitHub Check: Security Check
🔇 Additional comments (7)
packages/stack-shared/src/config/format.ts (7)
5-5: LGTM!The import of
OptionalKeysandRequiredKeysutility types aligns with their usage in the_NormalizesTotype definition and follows the project's pattern of importing specific utility types.
20-21: Improved type precision with utility types.The use of
OptionalKeysandRequiredKeysprovides better type safety by correctly distinguishing between optional and required properties in the normalized config type. The conditional handling for required keys that can be undefined is also correct.
169-183: Well-implemented utility functions for normalization checking.The
isNormalizedandassertNormalizedfunctions correctly identify normalized configs by checking for the absence of dot notation keys and null values. The assertion function follows TypeScript best practices with proper type narrowing.
145-160: Well-designed normalization options with clear documentation.The expanded
NormalizeOptionsprovides granular control over dot notation handling. The separation ofonDotIntoNonObjectandonDotIntoNulloptions allows for flexible configuration normalization strategies. The documentation clearly explains each option's behavior.
202-225: Correct implementation of dot notation handling logic.The normalization logic properly handles the different options for dot notation behavior:
- The "like-non-object" fallback correctly delegates to
onDotIntoNonObjectbehavior- The "empty-object" case properly sets an empty object with a break statement
- All switch cases use blocks as required by coding guidelines
- Error messages are descriptive and include relevant context
228-228: Correct propagation of normalization options.The options parameter is properly threaded through all helper functions (
normalizeValue,setNormalizedValue) to ensure consistent normalization behavior throughout the process.Also applies to: 233-233, 236-236, 240-240, 246-246
266-266: Comprehensive test coverage for new normalization options.The test updates properly validate:
- The
onDotIntoNonObject: "ignore"behavior in the main test case- Error scenarios with updated parameter names
- The new test case specifically covering dot notation into non-objects with "ignore" option
The expected results correctly match the documented behavior.
Also applies to: 280-280, 284-284, 287-287, 294-298
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
packages/stack-shared/src/config/schema.ts (1)
490-517: Avoid multipleas anycasts.The functions use multiple
as anycasts which violate coding guidelines. This issue was previously identified and should be addressed by improving type inference.
🧹 Nitpick comments (1)
packages/stack-shared/src/config/schema.ts (1)
1-1: Consider addressing the TODO comment.The comment suggests code quality concerns. If this file has become complex due to accumulated changes, consider refactoring it into smaller, more focused modules.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
apps/backend/package.json(1 hunks)packages/stack-shared/src/config/schema.ts(4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- apps/backend/package.json
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{ts,tsx}: TypeScript with strict types, prefertypeoverinterface
Avoid casting toany; Prefer making changes to the API so thatanycasts are unnecessary to access a property or method
Files:
packages/stack-shared/src/config/schema.ts
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{js,jsx,ts,tsx}: 2-space indentation, spaces in braces, semicolons required
Return promises withreturn await, no floating promises
Proper error handling for async code with try/catch
Use helper functions:yupXyz()for validation,getPublicEnvVar()for env
Switch cases must use blocks
Files:
packages/stack-shared/src/config/schema.ts
🧠 Learnings (1)
packages/stack-shared/src/config/schema.ts (3)
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use helper functions: yupXyz() for validation, getPublicEnvVar() for env
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : Avoid casting to any; Prefer making changes to the API so that any casts are unnecessary to access a property or method
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : TypeScript with strict types, prefer type over interface
⏰ 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). (5)
- GitHub Check: docker
- GitHub Check: restart-dev-and-test
- GitHub Check: docker
- GitHub Check: all-good
- GitHub Check: Security Check
🔇 Additional comments (6)
packages/stack-shared/src/config/schema.ts (6)
36-187: LGTM! Well-structured schema definitions.The schema definitions are comprehensive and well-organized. The removal of optional wrappers and enforcement of required keys for RBAC, API keys, auth, domains, and emails configurations improves schema strictness as intended.
190-304: LGTM! Excellent migration system implementation.The migration functions are well-designed with:
- Clear documentation about purpose and constraints
- Proper handling of different config levels
- Comprehensive test coverage for helper functions
- Logical migration steps for historical schema changes
The separation of concerns and the emphasis on reproducibility are particularly good practices.
312-489: LGTM! Comprehensive default configuration system.The default configuration objects are well-structured with explicit undefined values, and the applyDefaults function with dot notation support is excellently implemented with comprehensive test coverage.
520-578: LGTM! Well-implemented sanitization functions.The sanitization functions properly handle:
- Config level hierarchy with appropriate delegation
- SourceOfTruth normalization based on type
- Email theme/template merging with defaults
- Proper validation using assertNormalized
The implementation follows good patterns and maintains type safety.
580-784: LGTM! Comprehensive validation system.The validation functions implement sophisticated schema validation with:
- Proper error handling using Result types
- Advanced schema introspection and restriction
- Appropriate handling of deprecated properties
- Comprehensive validation for all schema types
The complexity is well-justified by the thorough validation requirements.
787-856: LGTM! Excellent TypeScript type system.The type definitions are well-structured with:
- Clear naming conventions for different config stages (override, incomplete, rendered)
- Proper use of advanced TypeScript utility types
- Comprehensive type assertions for validation
- Appropriate config level hierarchy
The type system provides excellent type safety and follows TypeScript best practices.
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (2)
packages/stack-shared/src/config/schema.ts (2)
26-31: Avoidas anycast in canNoLongerBeOverridden function.
500-527: Avoid multipleas anycasts.
🧹 Nitpick comments (1)
packages/stack-shared/src/config/schema.ts (1)
1-1: Consider proper refactoring instead of the self-deprecating comment.While the humor is appreciated, this TODO comment is unprofessional. Consider breaking down this file into smaller, focused modules (e.g.,
schema-definitions.ts,migration-utils.ts,validation-utils.ts, etc.) to improve maintainability.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
packages/stack-shared/src/config/schema.ts(4 hunks)packages/stack-shared/src/utils/objects.tsx(7 hunks)turbo.json(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- turbo.json
🚧 Files skipped from review as they are similar to previous changes (1)
- packages/stack-shared/src/utils/objects.tsx
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{ts,tsx}: TypeScript with strict types, prefertypeoverinterface
Avoid casting toany; Prefer making changes to the API so thatanycasts are unnecessary to access a property or method
Files:
packages/stack-shared/src/config/schema.ts
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{js,jsx,ts,tsx}: 2-space indentation, spaces in braces, semicolons required
Return promises withreturn await, no floating promises
Proper error handling for async code with try/catch
Use helper functions:yupXyz()for validation,getPublicEnvVar()for env
Switch cases must use blocks
Files:
packages/stack-shared/src/config/schema.ts
🧠 Learnings (1)
packages/stack-shared/src/config/schema.ts (3)
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use helper functions: yupXyz() for validation, getPublicEnvVar() for env
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : Avoid casting to any; Prefer making changes to the API so that any casts are unnecessary to access a property or method
Learnt from: CR
PR: stack-auth/stack-auth#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-28T23:25:51.701Z
Learning: Applies to **/*.{ts,tsx} : TypeScript with strict types, prefer type over interface
⏰ 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). (9)
- GitHub Check: docker
- GitHub Check: build (22.x)
- GitHub Check: all-good
- GitHub Check: restart-dev-and-test
- GitHub Check: build (22.x)
- GitHub Check: setup-tests
- GitHub Check: docker
- GitHub Check: lint_and_build (latest)
- GitHub Check: Security Check
🔇 Additional comments (6)
packages/stack-shared/src/config/schema.ts (6)
57-59: Clarify the intent of.isTrue().optional()pattern.The combination of
.isTrue().optional()is confusing. If a field is optional, it typically means it can beundefined. However, constraining it totruewhen present seems to indicate you want eithertrueorundefined, neverfalse. Consider using.oneOf([true])or documenting why this pattern is necessary.Also applies to: 69-69, 70-70
190-305: Well-structured migration functions with clear documentation.The migration functions are well-implemented with:
- Clear documentation about their purpose (database migrations only)
- Comprehensive test coverage
- Proper handling of nested properties with dot notation
- Good separation of concerns between different migration operations
307-484: Excellent implementation of defaults system with strong type safety.The defaults implementation demonstrates:
- Clever use of TypeScript's type system to ensure type safety
- Support for function-based defaults for dynamic key generation
- Comprehensive test coverage for edge cases including dot notation
- Clear separation between different config levels
530-588: Well-implemented sanitization functions with proper type safety.The sanitization functions correctly:
- Assert normalization before processing
- Handle sourceOfTruth type narrowing with proper type guards
- Merge default email themes/templates appropriately
- Maintain type safety throughout the chain
590-794: Comprehensive validation system with clear error/warning separation.The validation implementation excels in:
- Clear distinction between blocking errors and non-blocking warnings
- Thorough schema introspection with proper handling of nested types
- Good error messages that guide users
- Proper handling of the
canNoLongerBeOverriddenmetadata- Smart decision to prefer records over arrays for config structures
796-866: Excellent type definitions with comprehensive compile-time checks.The type system implementation:
- Provides clear types for each stage of config processing
- Uses
Expandfor better IDE tooltips and debugging- Includes compile-time assertions to catch type errors early
- Maintains clear separation between override, incomplete, and rendered configs
There was a problem hiding this comment.
Pull Request Overview
This pull request enhances the project configuration system with significant TypeScript utilities, improved validation mechanisms, and comprehensive support for currency/date operations. The changes modernize the config schema system with stricter type safety, better error handling, and granular control over configuration validation at different organizational levels.
- Enhanced TypeScript utilities: Added sophisticated type manipulation helpers, config schema introspection, and validation utilities in
types.tsxandschema-fields.ts - Improved configuration system: Refactored config override logic with migration support, sanitization functions, and stricter schema enforcement across project/branch/environment/organization levels
- New domain-specific utilities: Added currency conversion support and date interval arithmetic functionality
Reviewed Changes
Copilot reviewed 25 out of 25 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| turbo.json | Added new environment variables for Google AI, Discord integration |
| packages/stack-shared/src/utils/types.tsx | Major expansion with advanced TypeScript type utilities and assertion helpers |
| packages/stack-shared/src/utils/strings.tsx | Added typed string joining utilities with compile-time type safety |
| packages/stack-shared/src/utils/objects.tsx | Enhanced object manipulation utilities and improved type definitions |
| packages/stack-shared/src/utils/dates.tsx | New date interval arithmetic functions with schema validation |
| packages/stack-shared/src/utils/currencies.tsx | New currency handling utilities with Stripe integration support |
| packages/stack-shared/src/schema-fields.ts | Extensive schema system improvements with better introspection and validation |
| packages/stack-shared/src/helpers/emails.ts | Updated email template structure to include theme ID fields |
| packages/stack-shared/src/config/schema.ts | Massive refactor of config schema system with migration, validation, and sanitization |
| packages/stack-shared/src/config/format.ts | Enhanced config normalization with better error handling options |
| packages/stack-shared/src/config/README.md | Updated documentation with clearer technical explanations |
| docs/templates/overview.mdx | Fixed broken navigation links |
| apps/backend/src/route-handlers/smart-request.tsx | Fixed logic error in development key override validation |
| apps/backend/src/lib/projects.tsx | Updated trusted domains structure to use unique IDs |
| apps/backend/src/lib/permissions.tsx | Refactored to use new config override helpers |
| apps/backend/src/lib/email-rendering.tsx | Removed debug logging and cleaned imports |
| apps/backend/src/lib/config.tsx | Major refactor of config validation and override logic |
| apps/backend/src/app/api/latest/internal/email-themes/route.tsx | Simplified theme handling by removing automatic updates |
| apps/backend/src/app/api/latest/internal/email-templates/route.tsx | Updated to use new typed entry functions |
| apps/backend/src/app/api/latest/internal/email-templates/[templateId]/route.tsx | Simplified template update logic |
| apps/backend/src/app/api/latest/emails/render-email/route.tsx | Added error handling imports |
| apps/backend/scripts/verify-data-integrity.ts | Added flag to skip Neon projects in verification |
| apps/backend/prisma/seed.ts | Fixed missing brace in seeding logic |
| apps/backend/package.json | Added migration imports watcher to development workflow |
| .vscode/settings.json | Updated spell check dictionary |
Important
This PR enhances project config with advanced TypeScript utilities, improved validation, and support for currency conversions, while fixing bugs and refactoring for better schema enforcement.
This description was created by
for 68ea382. You can customize this summary. It will automatically update as commits are pushed.
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Documentation
Chores