Skip to content

Example of how phx-change events can get routed to the wrong components on reconnects, when a change in the component tree has changed server-side

Notifications You must be signed in to change notification settings

Torkan/lv-reconnect-issue

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

LvReconnectIssue

Steps to reproduce:

  • Start the app with mix phx.server
  • Go to localhost:4000
  • Type something in the text input field, so that it does not have the default value.
  • On line 11 in lib/lv_reconnect_issue_web/live/index.ex, change the <%# to <%=.
  • Restart the server.
  • When the client reconnnects, observe that the phx-change event meant for the form component, is instead routed to the new component, causing the view to crash and get restarted, and the changed form value on the client gets wiped.

About

Example of how phx-change events can get routed to the wrong components on reconnects, when a change in the component tree has changed server-side

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published