Kero van Gelder
Kero van Gelder
See also #2448
On Discord, Inoas suggested uri is a bit specific for stdlib. That it could be a separate lib (I'd say closer to gleam/http).
To what extent do you want to be compatible with uri_string:parse? `uri.parse` is gleam, and feeding strings on both targets to any library that needs a Uri should behave the...
and "ws:path" according to `URL` would have "path" as host. On Erlang, "path" is path. And I *want* it as path for `lustre_websocket` because I want to be able to...
and an example the other way round: "::" is accepted by current `uri.parse` on JS, but rejected by both Erlang `uri_string:parse` and JS `new URL`.