-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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.
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
View composer namespaced wildcards no longer work #44634
Comments
I'll take a stab at a PR. |
Yeah, I can confirm the issue. We need to work a bit more on |
I had a feeling it would be much faster for Nuno. 🤣 |
@jasonvarga @KennedyTedesco Can you test if the changes I've made fix the issue you were having in your application? It does fix the issue on the application you have prepared on the issue. |
@nunomaduro My application has lots of custom namespaces and composers using wildcards, and with your fix, everything works fine again. Thank you! |
Yup, fixes it for us too. Thanks @nunomaduro |
Thank you for the speedy turnaround! |
Description:
Using a view composer with a namespaced wildcard no longer works as of 9.36.0. Likely due to #44487 since it's all about views.
Using a complete wildcard still works.
View::composer('*', ...)
It's just the namespaced version that doesn't.
View::composer('namespace::*', ...)
Steps To Reproduce:
Here's a GitHub repo with the issue reproduced. Link to commit that adds the problematic bits:
https://github.com/jasonvarga/laravel-view-composer-issue/commit/1548cefdba11aa2c660eb2aab6eb5b5fef2d1958
The text was updated successfully, but these errors were encountered: