Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nuxt-convex-playground | 133fa24 | Commit Preview URL Branch Preview URL |
Feb 12 2026, 10:20 AM |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 04cb20c2c5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ), | ||
| ) | ||
| const allDocs = results.flatMap(r => r.docs) | ||
| const uniqueDocs = [...new Map(allDocs.map((d: unknown) => [(d as { _id: string })._id, d])).values()] |
There was a problem hiding this comment.
Apply limit after merging OR findMany results
When findMany receives OR-connected filters and a limit, each clause is paginated with that limit and then merged/deduplicated, but the merged array is returned as-is. This can return more rows than requested (for example, two OR branches can each contribute up to limit unique docs), which breaks callers that rely on bounded result sets; enforce the final limit after dedupe (and after sorting when sortBy is present).
Useful? React with 👍 / 👎.
14b2f65 to
a761d9c
Compare
commit: |
Summary
nuxt-convex/better-authwithcreateConvexHttpAdapter.convexdatabase provider for@onmax/nuxt-better-authvia thebetter-auth:database:providershook.Tests
pnpm dev:preparepnpm testpnpm typecheckNotes
@onmax/nuxt-better-auth(nuxt-modules/better-auth#106).