[5.6] Blade component aliases#22796
Merged
taylorotwell merged 1 commit intolaravel:5.6from Jan 15, 2018
sebastiandedeyne:blade-component-aliases
Merged
[5.6] Blade component aliases#22796taylorotwell merged 1 commit intolaravel:5.6from sebastiandedeyne:blade-component-aliases
taylorotwell merged 1 commit intolaravel:5.6from
sebastiandedeyne:blade-component-aliases
Conversation
This was referenced Feb 9, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a
componentmethod to Blade for registering component aliases. Blade components are one of my favorite additions to Laravel, but the syntax can be quite verbose sometimes. This adds an easy way to create component directives, for components that you're going to use all over your app.This PR also adds a shorter syntax, that assumes that you'll want to alias your component to the last part of the component path. This allows you to omit the second argument.
You lose explicitness though, so I could drop that from the PR if it's in the way.