refactor(bia-shared)!: 3.0.0 pure barrel + cross-repo schema-history archive - #64
Conversation
…ve to ./react (3.0.0) The root barrel (and ./articles) re-exported the ArticleRenderer React component, so any pure Node/server consumer importing the barrel for a type dragged in the `react` peer dependency (plus the "use client" boundary). Move ArticleRenderer to a new ./react subpath (@biboyang425/bia-shared/react), source-only like ./next/*. The root barrel and ./articles now expose only types + pure logic (Article type, excerpt, images, sanitize, slug helpers), so type-only imports stay React-free. BREAKING: consumers importing ArticleRenderer from the root or ./articles must switch to ./react. Bumped 2.0.0 -> 3.0.0. Sole in-repo consumer (BlogEditor) updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…er policy Copy the shared-table migration SQL from bia-roommate (29 files) and george (15 files) into docs/schema-history/ as an inert, read-only provenance archive. These are NOT runnable migrations and are never applied — the canonical append-only history is supabase/migrations/ and the live DB is the source of truth. The README records: the single-owner story (bia-admin owns migrations going forward; roommate/george supabase dirs are being deleted in parallel PRs), a per-file table of which archived migration created which shared table, a WARNING that three functions (enqueue_parcel_notification, admin_patch_parcel, admin_attach_parcels_to_shipment) have divergent bodies whose only canonical definitions live in supabase/migrations/, and a note that george's local set is internally inconsistent (001 students lacks the user_id that 010-014 FK against — that column actually came from roommate's shipping_user_link), so the archive is provenance, not a replayable history. CLAUDE.md's schema section now states this provenance and the single-owner policy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Warning Review limit reached
Next review available in: 56 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (53)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
…Url:./src shadowed the npm react package The ./react export subpath is unchanged (consumers still import @biboyang425/bia-shared/react); only the internal source directory moved, so that a bare `import * as React from "react"` no longer resolves to the local dir under baseUrl:./src (which broke next build's type-check). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
1 participant
Part 1 of the cross-repo cleanup (companion PRs land in bia-roommate and george).
bia-shared 3.0.0 (breaking)
ArticleRenderermoved to the new./reactsubpath (source-only, mirrorsnext/*), so Node consumers (george) can import types without dragging react/jsdom.isomorphic-dompurifyviasanitizeArticleHtml(pure, Node-isomorphic) — acceptable, documented.Schema-history archive (docs only)
docs/schema-history/{bia-roommate,george}/archives the 29 + 15 migration files whose DDL created most shared tables (students, parcels, shipments, squad_*, sublets, events...). Inert documentation, not runnable migrations.enqueue_parcel_notification,admin_patch_parcel,admin_attach_parcels_to_shipment) — only rootsupabase/migrations/is canonical.supabase/from bia-roommate and george and add CI guards, making this repo the single migrations owner in fact.Merge order
Merge THIS first — publishing 3.0.0 unblocks the consumer bumps in the bia-roommate and george PRs.
Tests: bia-shared 67 + bia-admin 355 | 25 skipped green; tsc clean.
🤖 Generated with Claude Code