-
Notifications
You must be signed in to change notification settings - Fork 11k
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
[Request] Blade autoescaping and better documentation on @show/@stop #978
Comments
No sections don't know if they are being overridden or not. That would make no sense. |
But, consider this blade:
and this:
calling:
Using |
Well, of course you have to put @show on teh first one. |
That's how it works. It works well, lots of people use it like that all the time and there is no other possbile way it could even work. The autoescape thing is another issue. |
So it does have to know it is the first one... |
Im having the this issue too , following this reciepe :
will output this Top but it actually only shows : |
Autoescaping sections:
Also providing a way to bypass the autoescaping for some entries. I would feel safer working with white lists instead of black ones.
Also, the docs need a better insight on Blade. There's no clue there about that new
@show
@stop
thingy. I tried playing around with it and it just seems that it doesn't work well, unless you do exacly what the doc shows (@show
on templates,@stop
on pages). Does that mean the sections have to know if they will be overrided or not? If that's the case (i really don't know for sure), I think that's kinda limiting.For last, and that's more of an observation than a request, I will really miss the non-blade syntax:
I find php a very good templating syntax already. Wish i could use blade's power directly in it :p
The text was updated successfully, but these errors were encountered: