3 ms·
You can easily change the config to make the Blade tags work as they previously did. I'm unhappy about this change as well though. It's very reminiscent of some
by johnmaguire2013 12y ago
You can easily change the config to make the Blade tags work as they previously did. I'm unhappy about this change as well though. It's very reminiscent of some design decisions PHP has taken:
1. Create feature X.
2. Users don't understand feature X, and use it when they should be using feature Y (for safety.)
3. Update the API so that feature X does what feature Y did, and create feature Z that now does what feature X did.
4. Old users using feature X incorrectly are now protected, while users who correctly used feature X must now convert to feature Z.
- e12e 12y agoNot being familiar with Laravell, having a look at[1], I see what you mean: > In Laravel 4 Blade included the following two styles: {{ and {{{. > The double curly bracket was a raw echo and the triple curly bracket escaped. > > Now both the double and triple curly brackets escape the variable and a new {!! $var !!} is for raw. I'd argue that having unescaped output be shorter/easier than escaped output was probably a design error in earlier versions -- but I'm not sure I like the "fix"... If it was a green-field design, I must admit I like the "danger!"-feel that unescaped output has in L5 though. [1] https://laravel-news.com/2015/01/laravel-5/ https://laravel-news.com/2015/01/laravel-5/