Don't register listener for custom directive #8259
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.
Livewire supports "wildcard" event listeners like this:
If what comes after
wire:
isn't a built-in directive, Livewire will register an event listener for it and fire the method when the event is fired. (This is actually howwire:click
itself works - it's just a wildcard event)However, if you register a custom directive like this:
Livewire will encounter
<div wire:sort
and not only run your custom directive code, but also register a listener for thesort
event.This PR disables that behavior so that errant custom directive names don't cause odd behavior with native events.