Skip to content

Capture Livewire component name on Livewire update requests #208

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 25 commits into from
Jul 3, 2025
Merged

Capture Livewire component name on Livewire update requests #208

merged 25 commits into from
Jul 3, 2025

Conversation

jessarcher
Copy link
Member

@jessarcher jessarcher commented Jun 27, 2025 •
edited
Loading

As a first step towards improving Livewire support, this PR does the following:

  • Adds some basic Livewire 2 and 3 tests
  • On Livewire update requests, sets the route action to the name of the Livewire component, instead of Livewire's internal controller name.

Note: requests that handle multiple components will have the component names comma-separated.

Possible future improvements:

  • Handle multiple component actions and multiple components in a single request - probably with a new event type which can be nested inside the controller action in the timeline
  • Pass the trace ID from the original request so it can be used on subsequent update requests (this could get tricky on batch requests)

@jessarcher jessarcher force-pushed the livewire branch 3 times, most recently from 1e2da54 to 3f8cec9 Compare June 27, 2025 12:10
@ralphjsmit
Copy link

ralphjsmit commented Jun 28, 2025 •
edited
Loading

As a regular Livewire-user, if you could manage to link Livewire-updates to a Request timeline, that would be super-powerful. So that you can see "user loaded page X at YY:ZZ", and subsequently made 20 /livewire/update calls (interactions), each with their payload visible (called methods, dispatched events). This would – for pretty much the first time – bring insight into how a Livewire-component has "evolved" through user interactions to a final state until e.g. an exception occurs.

@jessarcher jessarcher force-pushed the livewire branch 3 times, most recently from 9797d2f to 1344b1c Compare June 30, 2025 01:28
@jessarcher jessarcher force-pushed the livewire branch 4 times, most recently from 8ded4ce to cc54311 Compare July 1, 2025 07:13
@jessarcher jessarcher changed the title Improve Livewire support Capture Livewire component name on Livewire update requests Jul 1, 2025
@jessarcher jessarcher marked this pull request as ready for review July 1, 2025 08:02
@jessarcher jessarcher marked this pull request as draft July 2, 2025 01:47
jessarcher
jessarcher commented Jul 2, 2025
View reviewed changes
@jessarcher jessarcher marked this pull request as ready for review July 2, 2025 03:29
jessarcher
jessarcher commented Jul 2, 2025
View reviewed changes
@jessarcher jessarcher enabled auto-merge (squash) July 3, 2025 02:26
@jessarcher jessarcher merged commit 7897564 into 1.x Jul 3, 2025
25 checks passed
@jessarcher jessarcher deleted the livewire branch July 3, 2025 02:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@timacdonald timacdonald timacdonald approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@jessarcher @ralphjsmit @timacdonald
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy