[5.x] Add blade @cascade
directive
#10674
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using blade the cascade data is only available in the entry's main template, and the layout if you're using
@extends
. This can leave situations where you don't have quick access to the cascade data (without workarounds), for example:This PR adds a new blade directive called
@cascade
which will add cascade data to the current scope.It works in exactly the same way as the
@props
directive used in blade components, with the ability to require certain values and/or provide default fallback values:Specifying only the data you want is probably the best way to go in most situations, especially in components where the cascade variables could overwrite prop variables. However it is also possible to add the entire cascade if needed: