Rick, +1 on making this change if you would like, as a slack or dev support task. We would appreciate it.
I (somewhat strongly) suggest that the socket_url be calculated dynamically in the browser, and not as a build time value.
In order to support the charm, the logic in the JS needs to be backwards compatible. That is, it must support either a full url (as it does now, and as the charm provides it) or what I think you would want: only a port and path.
full url -> unchanged
:port/path -> ws://[HOSTNAME]:port/path
Rick, +1 on making this change if you would like, as a slack or dev support task. We would appreciate it.
I (somewhat strongly) suggest that the socket_url be calculated dynamically in the browser, and not as a build time value.
In order to support the charm, the logic in the JS needs to be backwards compatible. That is, it must support either a full url (as it does now, and as the charm provides it) or what I think you would want: only a port and path.
full url -> unchanged :port/path
:port/path -> ws://[HOSTNAME]