Skip to content

POC: Inspecting LiveVIew#383

Closed
GuzekAlan wants to merge 2 commits into
mainfrom
348-inspecting-livecomponents
Closed

POC: Inspecting LiveVIew#383
GuzekAlan wants to merge 2 commits into
mainfrom
348-inspecting-livecomponents

Conversation

@GuzekAlan
Copy link
Copy Markdown
Contributor

No description provided.

@GuzekAlan GuzekAlan linked an issue May 13, 2025 that may be closed by this pull request
Copy link
Copy Markdown
Member

@kraleppa kraleppa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like your approach - it's really creative and having components inspection working not only for DevTools is game-changer.

However I have thought. We are already sending events via debugged application websocket (associated with highlighting). Now we'll have even more events coming from server to client and we also have client server communication (the post request you make)

Maybe we should create a separate websocket for LiveDebugger communication and move whole LiveDebugger communication there? In the browser we should have phoenix socket already defined and we should be able to easily declare a new socket on the server side (since we have a new endpoint)

Comment thread assets/js/client.js
Comment thread mix.exs
{:phoenix_live_view, "~> 0.20 or ~> 1.0"},
{:igniter, "~> 0.5 and >= 0.5.40", optional: true},
{:bandit, "~> 1.6", only: [:dev, :test]},
{:cors_plug, "~> 3.0"},
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really necessary to add this dep?

@GuzekAlan
Copy link
Copy Markdown
Contributor Author

@kraleppa

Maybe we should create a separate websocket for LiveDebugger communication and move whole LiveDebugger communication there? In the browser we should have phoenix socket already defined and we should be able to easily declare a new socket on the server side (since we have a new endpoint)

As I understand we will create a separate socket which will be registered using our client.js which is conditional based on browser_features config. It is a good idea. We could create Phoenix.Channel even for this type of streaming events which might make highlighting and inspecting more smooth.

@kraleppa
Copy link
Copy Markdown
Member

@GuzekAlan exactly

@kraleppa kraleppa closed this May 21, 2025
@kraleppa kraleppa deleted the 348-inspecting-livecomponents branch February 3, 2026 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inspecting LiveComponents

2 participants