Skip to main content

Laravel v5.4.29 is Released with Two New Blade Directives on 19th July

Laravel V5.4.29 is now released and available. This is a maintenance release but it includes two new Blade Directives, a --force option on some of the “make” commands, and more.

New @auth and @guest Directives

The @auth directive allows you to simplify the check to see if a user is logged in. For example, in the past you might use:
@if(Auth::check())
   You are logged in.
@endif
Now with the @auth directive, this can be simplified to:
@auth
   You are logged in.
@endauth
It also supports the Guard to use as the first parameter:
@auth('admin')
    You are logged in through admin guard
@endauth
The other new directive is @guest which is the inverse:
@guest
   Welcome Guest
@endauth

v5.4.29 Complete Changelog

Added

  • Added ManagesFrequencies::twiceMonthly() method (#19874)
  • Added RouteCollection::getRoutesByName() method (#19901)
  • Added $expiresAt parameter to CallbackEvent::withoutOverlapping()(#19861)
  • Support keeping old files when testing uploads (#19859)
  • Added --force option to make:mailmake:model and make:notification(#19932)
  • Added support for PostgreSQL deletes with USES clauses (#20062f94fc02)
  • Added support for CC and BBC on mail notifications (#20093)
  • Added Blade @auth and @guest directive (#20087#20114)
  • Added option to configure MARS on SqlServer connections (#20113c2c917c)

Changed

  • Support object items in Arr::pluck() (#19838#19845)
  • MessageBag interface now extends Arrayable (#19849)
  • Made Blueprint macroable (#19862)
  • Improved performance for Arr::crossJoin() (#19864)
  • Use the correct User model namespace for new policies (#19965a7094c2)
  • Consider scheduled event timezone in inTimeInterval() (#19959)
  • Render exception if handler can’t report it (#19977)
  • Made MakesHttpRequests::withServerVariables() public (#20086)
  • Invalidate session instead of regenerating it when logging out (#20107)
  • Improved InvalidPayloadException error message (#20143)

Fixed

  • Don’t re-escape a View instance passed as the default value to @yield or @sectiondirectives (#19884)
  • Make sure migration file is loaded before trying to rollback (#19922)
  • Fixed caching issue in mix() (#19968)
  • Signal alarm after timeout passes (#19978)

Comments

Popular posts from this blog

Design Tools to Help You Create Your Next Project- Part 3

Coolors Coolors   is a super fast color scheme generator. You can explore thousands of pre-existing color schemes (each one features five colors). Or, you can generate your own in a matter of minutes. Once you go to the “generate” page, hit the space bar to start with a different color scheme, and then you can adjust each color’s hue, saturation, and brightness accordingly. Web Gradients Web Gradients   is a collection of almost 200 background gradients, created by the  itmeo  team. You can use each of these content backdrops for any part of your website. You’ll find a .PNG version of each gradient, as well as easy-to-copy CSS3 crossbrowser code. Bonus: there are even curated packs for  Sketch  &  Photoshop . Color Hunt On  Color Hunt , browse through countless palettes, comprised of four colors each. You can browse and sort through the list based on what’s hot and popular, or just pick “random” and see what comes u...

WordPress 4.8 Release Candidate 2 on June 1, 2017

The second release candidate for WordPress 4.8 is now available. To test WordPress 4.8, you can use the  WordPress Beta Tester  plugin or you can  download the release candidate here  (zip). We’ve made  a handful of changes  since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the  Beta 1 ,  Beta 2 , and  RC1  blog posts. Think you’ve found a bug?  Please post to the  Alpha/Beta support forum . If any known issues come up, you’ll be able to  find them here . Happy testing!                                                                                                                   ...

Node.js + MySQL Example: Handling 100's of GigaBytes of Data

Through this Node.js & MySQL example project, we will take a look at how you can efficiently handle  billions of rows  that take up  hundreds of gigabytes  of storage space.                          Secondary goal with this article is to help you decide if Node.js + MySQL is a good fit for your needs, and to provide help with implementing such a solution. The actual code we will use throughout this blogpost  can be found on GitHub . Why Node.js and MySQL? Use MySQL to store the distributed tracing data of the users of our  Node.js Monitoring & Debugging Tool  called Trace. We chose MySQL, because at the time of the decision, Postgres was not really good at updating rows, while for us, updating immutable data would have been unreasonably complex. Most think if anyone has millions/billions of rows, they should use a NoSQL solution such as Cassandra or Mongo. Unfortun...