Skip to content
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

compilation warnings (from a shadow-cljs project depending on [bidi "2.1.4"]) #189

Closed
gmp26 opened this issue Nov 9, 2018 · 3 comments · Fixed by #190
Closed

compilation warnings (from a shadow-cljs project depending on [bidi "2.1.4"]) #189

gmp26 opened this issue Nov 9, 2018 · 3 comments · Fixed by #190

Comments

@gmp26
Copy link

gmp26 commented Nov 9, 2018

------ WARNING #1 --------------------------------------------------------------
 File: bidi/bidi.cljc:29:12
--------------------------------------------------------------------------------
  26 | actually a valid UUID (this is handled by the route matching logic)."
  27 |   [s]
  28 |   #?(:clj (java.util.UUID/fromString s)
  29 |      :cljs (cljs.core.UUID. s)))
------------------^-------------------------------------------------------------
 Wrong number of args (1) passed to cljs.core.UUID
--------------------------------------------------------------------------------
  30 | 
  31 | ;; When forming paths, parameters are encoded into the URI according to
  32 | ;; the parameter value type.
  33 | 
--------------------------------------------------------------------------------
@SevereOverfl0w
Copy link
Contributor

That's interesting. Is there a function in clojurescript which turns a string into a uuid?

@gmp26
Copy link
Author

gmp26 commented Nov 9, 2018

Yes. https://cljs.github.io/api/cljs.core/uuid

@thheller
Copy link

FWIW you are only seeing this in shadow-cljs currently since CLJS does not handle symbols with a dot in properly.

See https://dev.clojure.org/jira/browse/CLJS-712 and vote

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants