Conversation
…ct' into 'constructor' to follow Angular convention
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request refactors test code in the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit f7f3215
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
🎯 Changes
Refactors the three
effect()calls inwith-persist-query-client.test.tsfrom the class-field assignment (_ = effect(...)) pattern into an explicitconstructor()body, matching the convention used in our own Angular documentation.Before
After
Why
The Angular official signals guide explicitly calls out the constructor as the recommended place to register an
effect:The same pattern is already used in our own guide at
docs/framework/angular/guides/paginated-queries.md, so moving the tests to match keeps the codebase internally consistent.This mirrors the same refactor applied to
inject-queries.test.tsin #10537.Verification
@tanstack/angular-query-persist-client— 5 tests passed, 1 todo, 0 type errors✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit