Add MariaDB/PostgreSQL support and 100% test coverage - #1
seonghobae with Copilot wants to merge 7 commits into
Conversation
… gitignore, update undici/brace-expansion
…nvalid CLI flags, audit double-encoding
|
Warning Review limit reached
Next review available in: 14 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (50)
Comment |
Superseded by issue #2 for a migration-safe rebuild from current protected
develop.The branch contains valuable test coverage and multi-provider exploration, but its current exact head cannot be merged safely. Current-head Security Scan fails on fixable
brace-expansion,postcss,undici, and frontendreact-routerfindings. More importantly, this branch changes the productiondb:migrate:deploypath fromprisma migrate deploytoprisma db push --skip-generate, and the PostgreSQL-specific deployment path also usesdb pushdespite shipping an explicit migration. That converts a reviewed migration workflow into runtime schema drift.The provider schemas also replicate physical single-word table names such as
users,files, andfolders; these violate the CWL database naming contract requiring descriptive two-or-more-wordsnake_caseobject names. Multi-valued JSON fields also need a deliberate 1NF/3NF review instead of being copied across four provider schemas without a normalization decision.Issue #2 preserves the useful work and defines the canonical rebuild: port the tests first, regenerate patched locks, converge on one provider-neutral logical schema, use explicit reversible migrations, normalize relational data to 3NF, validate upgrade/rollback on MySQL/MariaDB/PostgreSQL/SQLite, and only then merge/release. Keep this branch available as source material until those tests/provider deltas have been absorbed.