Conversation
…lving 'provideIsRestoring' value with 'injector' option
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR adds a new test case to the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 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 unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit fdcc540
☁️ 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 📦
|
2074bc3 to
fdcc540
Compare
🎯 Changes
Add a test that verifies
injectIsRestoringresolves the value provided viaprovideIsRestoringwhen theinjectoroption is used (i.e., outside an injection context).The existing tests covered:
falseinside injection contextfalsewithinjectoroption (outside injection context)The missing matrix cell — provided signal value with
injectoroption — is now covered. This guarantees theinjector.get(IS_RESTORING)path correctly resolves through the user-registered DI tree, not just the default factory.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit
injectIsRestoringutility with additional validation of the injector option path configuration.