Conversation
…t to '@component' + 'render' pattern
|
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)
📝 WalkthroughWalkthroughA test file refactored to render an Angular component with Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 af91d7c
☁️ 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
Rewrites the main test in
inject-infinite-query.test.tsto use a@Component+@testing-library/angular'srenderinstead of callingTestBed.runInInjectionContextand asserting on the signal value viaexpectSignals. The assertion now checks the rendered DOM text, which mirrors how a user actually observesinjectInfiniteQueryin an Angular component.Mirrors the approach taken for
injectIsFetchingin #10556 andinjectIsMutatingin #10557.Before
After
Why
examples/angular/*(readonly query = injectInfiniteQuery(...)).readonlyfields on the test component follow the convention used in our Angular examples.injection contextdescribe block (NG0203 throw / passing an injector) is kept as-is — those checks don't need a rendered component.Verification
@tanstack/angular-query-experimental— 209 tests passed, 0 type errors✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit