Skip to content

[12.x] Fix Blade nested default component resolution for custom namespaces #55874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
May 27, 2025
Merged

[12.x] Fix Blade nested default component resolution for custom namespaces #55874

merged 1 commit into from
May 27, 2025
+53 −0

Conversation

daniser
Copy link
Contributor

@daniser daniser commented May 27, 2025 •
edited
Loading

Follow up #52669, nested default component class cannot be resolved if these conditions apply:

  • it is within a folder with same name as a class;
  • custom namespace is used.

@taylorotwell taylorotwell merged commit d070432 into laravel:12.x May 27, 2025
61 checks passed
@daniser daniser deleted the fix/nested-default-component-resolution branch May 27, 2025 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@daniser @taylorotwell