-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
back ~r Uri type with goog.Uri #16
Comments
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:
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?).
The text was updated successfully, but these errors were encountered: