Repository navigation
test(nextly): count the stripped batch row as processed, not just error-free - #1808
Conversation
…or-free A row skipped without being accounted for would also report no errors, so the case asserts the successful count, the failed count and the id.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe integration test now verifies that an unelevated protected-field batch update succeeds, reports no failures or errors, and returns the updated entry ID. ChangesBulk update access
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to The PR improves coverage of the no-op batch result without changing production behavior. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the test change and states that no changeset is needed. However, it does not follow the repository template because it omits the required Summary, Type of change, Related issues, Test plan, Checklist, Screenshots / recordings, and Notes for reviewers sections. Resolution Update the description to use the repository template. Add the missing sections, mark the applicable test-only or refactor/chore classification, document the test commands or verification performed, and complete the checklist items. Keep the existing explanation under Summary or Changeset as appropriate.
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 ESLint
packages/nextly/src/domains/collections/__tests__/bulk-update-override-access.integration.test.tsESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. 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 |
@nextlyhq/adapter-drizzle
@nextlyhq/adapter-mysql
@nextlyhq/adapter-postgres
@nextlyhq/adapter-sqlite
@nextlyhq/admin
@nextlyhq/admin-css
@nextlyhq/blocks-engine
@nextlyhq/blocks-react
@nextlyhq/builder
create-nextly-app
@nextlyhq/eslint-plugin
nextly
@nextlyhq/plugin-form-builder
@nextlyhq/plugin-page-builder
@nextlyhq/plugin-sdk
@nextlyhq/plugin-seo
@nextlyhq/storage-s3
@nextlyhq/storage-uploadthing
@nextlyhq/storage-vercel-blob
@nextlyhq/ui
commit: |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
What
Review on #1806, after it merged: the stripped un-elevated row asserted only
errors: [], which a row skipped without being accounted for would also satisfy. The case now assertssuccessful: 1,failed: 0and the row's id, so it proves the row was processed as a no-op.Changeset
None. Test-only.
Summary by CodeRabbit