Open sgrove opened 9 years ago
agree - cljs.core/uri? is defined and hardcoded to goog.Uri since 1.9. I understand that transit-js should neither depend on goog.Uri nor provide an explicit uri handler, but it seems like transit-cljs should align to clojurescript
perhaps this is why:
(= (goog.Uri. "http://localhost:8080/a?b#c")
(goog.Uri. "http://localhost:8080/a?b#c"))
=> false
(= (java.net.URI. "http://localhost:8080/a?b#c")
(java.net.URI. "http://localhost:8080/a?b#c"))
=> true
Note transit-java and transit-clj also decline to read to java.net.URI (in disalignment with the language uri? predicate), instead reading as cct.Uri
URIs as tagged values aren't very useful generally speaking, so right now I'm doing:
Would be nice to actually have this built into transit-cljs, though I'm not sure what the implications for running anywhere that goog.closure has a hard time reaching (self-hosting issue?).