-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Not working with illuminate/view 11.8/11.9/11.10 #74
Comments
It's true, thank you! Solved issue by doing after install this package:
|
They moved away from grabbing the container via |
Should probably add the requirement for illuminate/view into the README at the very least, no? Right now the out-of-box installation experience is a broken library with an odd error. |
Not even into the README - into the composer.json. Just change the version range allowed for this library. I might even raise a PR for that here, as a temporary measure. |
Same goes for 10.48.11 and up. |
Thanks for the issue, please resolve |
Its work for me |
I'm on view v10.48.20 Ended up doing something like this to get it working and it should work on v11.8+ too
https://github.com/illuminate/view/blob/master/ViewServiceProvider.php#L165 |
Thanks whis work for me on blade v11.25.0 |
As ALameLlama said, it's enough to instantiate the singleton Illuminate Container before/when instantiating Jensseger's Blade. You can also do that by simply calling Container::getInstance(), i.e. i.e. a possible solution for Jenssegers would be to change the first line of Blade::__construct:
|
With illuminate/view 11.7, it works fine. That's the current workaround, just require
"illuminate/view": "~11.7.0"
.illuminate/view 11.10:
illuminate/view 11.9:
illuminate/view 11.8:
The text was updated successfully, but these errors were encountered: