Phoenix_live_view: Client should send its version to LiveView server

Created on 29 May 2020  路  3Comments  路  Source: phoenixframework/phoenix_live_view

The server should warn if the versions do not match. Note, however, in cases LiveView is pre-bundled, such as in the LiveDashboard, this can cause conflicts. We may need a way to opt-out of the warning. Another option is to have the server send the version and the client warn, but the warning may be hidden.

Most helpful comment

I'm thinking the versioning refers to the same version of LiveView on the JS side and the Phoenix side? I've been in the position where I do update via mix.deps but forget to also update the node modules. Is this the versioning mismatch that this issue is about?

All 3 comments

Would the implementer control the versioning, since some changes may require a reloaded client and others may not? (Edit: I'm probably misunderstanding what kind of versioning this is about :D)

I'm thinking the versioning refers to the same version of LiveView on the JS side and the Phoenix side? I've been in the position where I do update via mix.deps but forget to also update the node modules. Is this the versioning mismatch that this issue is about?

Yes!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

josevalim picture josevalim  路  3Comments

LightningK0ala picture LightningK0ala  路  5Comments

jamilabreu picture jamilabreu  路  6Comments

drapergeek picture drapergeek  路  5Comments

lukegalea picture lukegalea  路  3Comments