- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bump illuminate/support to 5.5 #1962
Conversation
results in:
|
The bump to 5.5 cased issues for my current project. In the following blade template, the last @php (right before $link) did not convert to <?php in the blade cache. Note sure if this is a 5.5 issue or there is a change I need to make with my code to make it compatible.
Was able to workaround by forcing 5.4 in composer:
|
Hmm. I did some testing and came across the same issue. It appears to be a problem with the shorthand PHP directive. I don't really understand what is causing it though. In some cases, it works just fine, but in others, not. |
@patram1121 I think you need a closing
And FWIW, using this blade feature frequently may be a signal that you have too much logic embedded within your template. See Blade Docs |
@Log1x I am pretty sure there isn't an $app container in Sage. Thus the error. The
|
Just dawned on me about the other Sage components, Those two packages need to be updated for this PR to play nice. |
I'll give that a shot and do some testing and if all is well I'll do a PR over that way too so we can hopefully get this bumped. |
@Log1x I have a 5.5 install running with no problems so far. Upgrading across the board (lib, installer, sage) doesn't have any ill effects. The Coincidentally, this is not the first time something like this has come up (ie: cherry-picking Illuminate components). Take a look at Matt Stauffer's Torch. They have been trying to get Artisan support to work without downloading the entire package as well. This just won't work without Illuminate\Foundation, which doesn't have composer.json to install from. And weirdly, Laravel Lumen has it's own version of Artisan piecemealed together and is kind of flakey. Seems they couldn't get around that either. |
@Log1x I found a workaround for getting the Blade In // Set the Facade application container to the Sage Container
\Illuminate\Support\Facades\Facade::setFacadeApplication(sage()); This not only fixes the |
* roots/master: (41 commits) Add uglifyjs plugin (roots#2070) Add missing trailing commas in 2f51b51 Run autoprefixer before minification Enable source comments in Sass Fix travis CI build error (missing trailing comma) Tweaked SVGO settings Make template() compatible with wp admin 9.0.1 Update to Bootstrap 4.1.1 Remove useless whitespace Auto-detect scheme Close roots#2028 - Increase priority on comments_template filter Remove Font Awesome reference [ci skip] Bump sage-lib Close roots#1962 - Bump to Laravel 5.6 Remove php blade shorthand Stable vs dev install messaging, ref roots/docs#140 [ci skip] Update some dependencies Update CHANGELOG [ci skip] Bootstrap 4.1.0 ...
Some new goodies with the release of Laravel 5.5