Skip to content

feat: add collection.name to TimelineMoment#409

Merged
techeng322 merged 1 commit into
mainfrom
techengme/myc-5025-add-collectionname-to-timelinemoment-type
Jul 16, 2026
Merged

feat: add collection.name to TimelineMoment#409
techeng322 merged 1 commit into
mainfrom
techengme/myc-5025-add-collectionname-to-timelinemoment-type

Conversation

@techeng322

Copy link
Copy Markdown
Collaborator

Summary

  • TimelineMoment gains a collection: { name: string } field, matching the RPC change in in_process_database PR github ci/cd for test #25.
  • Regenerated src/lib/supabase/types.ts for build_moment_json's new optional p_collection_name param (single overload, no duplicate Args shape now that the DB migration drops the old signature first).

Test plan

  • Merge/apply in_process_database PR github ci/cd for test #25 to the target Supabase project first
  • GET /timeline and confirm each moment includes collection.name
  • Typecheck passes (pnpm build / tsc)

/timeline moments now include a collection field (in_process_database#25).
Adds collection: { name } to TimelineMoment and regenerates Supabase types
for build_moment_json's new p_collection_name param.
@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
in-process-api Ready Ready Preview Jul 16, 2026 5:17pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@techeng322, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b30b241e-9318-405d-995e-96750877015d

📥 Commits

Reviewing files that changed from the base of the PR and between 241eba2 and a51efb5.

📒 Files selected for processing (2)
  • src/lib/supabase/types.ts
  • src/types/moment.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch techengme/myc-5025-add-collectionname-to-timelinemoment-type

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

Comment @coderabbitai help to get the list of available commands.

@techeng322
techeng322 merged commit 0b6bcd4 into main Jul 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant