Re: [whatwg/url] Expose a URLHost class to JavaScript (#288)

mikewest left a comment (whatwg/url#288)

> I think we have to be very careful about playing favorites with schemes. The fact that we have special schemes to begin with is rather unfortunate. I'd rather figure out building blocks that work well for everyone.

That's a reasonable desire. I feel like STUN and TURN scheme are defensible to add to the platform more centrally given how widely relied-upon they are, but I'm also in favor of providing the primitives that let them define behavior without inexplicable string concatenation.

Do you think both a `URLHost` and `URLHostAndPort` would be helpful? Or would you like to provide some spelling of the latter whose port could simply be ignored if irrelevant to the use case?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/288#issuecomment-3351077251
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/pull/288/c3351077251@github.com>