docs: explain BroadcastsGlobally and Laravel event listeners - #545
Open
shanerbaner82 wants to merge 1 commit into
Open
shanerbaner82 wants to merge 1 commit into
shanerbaner82 wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
The v4 Events page only explained component listeners, leaving it unclear when native events also reach Laravel listeners. Document NativePHP’s
BroadcastsGloballyinterface with anAppServiceProviderlistener and a custom event example.Clarifies payload versus event-object delivery, constructor requirements, EDGE versus WebView behavior, and how this differs from Laravel’s
ShouldBroadcastand background execution.Validation: documentation rendering tests passed locally (3 tests, 5 assertions); verified the new section in Chrome on the local docs site;
git diff --checkpassed. The PR contains only the Events documentation change.