You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an external package which service provider manually registers a few Blade components into the default BladeCompiler instance (through the Blade facade).
But, as long LaravelGettext allocates his own BladeCompiler, it is not inited in the same way and fails to compile the views as soon as it finds a reference to one of the expected component.
The most obvious fix should be to replace the locally allocated BladeCompiler with calls to the default Blade facade (tested and working), but I'm not entirely sure how it behaves with the handling of "domains"...
The text was updated successfully, but these errors were encountered:
I have an external package which service provider manually registers a few Blade components into the default BladeCompiler instance (through the Blade facade).
But, as long LaravelGettext allocates his own BladeCompiler, it is not inited in the same way and fails to compile the views as soon as it finds a reference to one of the expected component.
The most obvious fix should be to replace the locally allocated BladeCompiler with calls to the default Blade facade (tested and working), but I'm not entirely sure how it behaves with the handling of "domains"...
The text was updated successfully, but these errors were encountered: