Repository navigation
Register discovered package providers again - #255
JonasPardon wants to merge 1 commit into
Conversation
The package manifest's providers were spliced into the provider list as separate strings instead of as one group, so collapse() skipped them and no discovered provider was registered when app.loadDiscoveredPackages is enabled. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. Walkthrough
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk remains from the reviewed change. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
With
app.loadDiscoveredPackagesenabled, no discovered package provider gets registered onwip/1.3.0a6b24e("Laravel 10 changes") dropped the brackets around the manifest's providers inApplication::registerConfiguredProviders():That splices each provider class in as a separate string, between the
Illuminate\group and the other providers.collapse()only flattens arrays and skips anything else, so those strings never reachProviderRepository::load(). Laravel 12 still passes them as one group ([…->providers()]), which is what this restores. The default (loadDiscoveredPackages => false) is unaffected.Applicationwith a discovered provider and checks that it gets registered. It fails without the change.🤖 Generated with Claude Code
Summary by CodeRabbit