Hey, all. Trying to work out the conversion of this JS to CLJS: $(function() $("#datepicker").datepicker();});

I've gotten pretty close but can't seem to get the wrapping $(function()...) part.

I have: (js/$ (fn [] (-> (js/$ ".datepicker") (.datepicker))))

Which results in: return function() {return $(".datepicker").datepicker();};

So I don't know what's happening to the outer js/$.

Has anyone managed to get React Router to work via NPM imports?

@blake.watson code seems correct, except for the #-`.` swap. could it be simply that?

@vemv Oh, I'm switching between ID and class selectors, is all. I want $(function() $(".datepicker").datepicker();});

I don't think it's working. I've got two problems whenever I do something like this: I don't know if I have the js->cljs transliteration right, and I don't know if it's actually being called, or called at the right time.

trying out things at the repl can help

that way you don't depend so much on timing

i.e you remove need for $(function()) wrapping

Do you? Like, I can put that js into the console after the page has rendered and it will work.

I mean, just for the purpose of figuring out things you can:

load the page, without this cljs code

interact w/ page via repl

Ooh. My CLJS tab is working all of a sudden.

Wait, so the code DOES work. Cool. It's just a matter of figuring out where it should go, then.

So I have a react app, and it's building a screen from data with all the controls. I have it at the bottom of the render- function but that's not right, I guess.

A React-created element that responds to the $(".datepicker") selector can exist/disappear as things are re-rendered

i.e. through the 'component lifecycle'

that could be biting you

Right, that's always been my confusion.

I'm trying to use a npm dep in my project and getting:

(fig-start)
Figwheel: Starting server at 
Figwheel: Watching build - dev
Figwheel: Cleaning build - dev
Compiling "resources/public/js/app.js" from ["src" "dev"]...
Failed to compile "resources/public/js/app.js" in 32.571 seconds.
----  Exception    ----
  Assert failed: cljs.analyzer/foreign-dep? expected symbol got "graphql-voyager"
(symbol? dep)
----  Exception Stack Trace  ----

is there a clojurescript doc that describes why people keep using strings in require blocks?

I mean, that never looked right to me

@noisesmith idea might have come from https://code.thheller.com/blog/shadow-cljs/2017/09/15/js-dependencies-going-forward.html

@noisesmith Its in one of the guides

@alexisvincent yeah I found it here https://clojurescript.org/news/2017-07-12-clojurescript-is-not-an-island-integrating-node-modules

but if cljs is complaining maybe you need a newer version?

its to support requires like tis “sdfsdfsdf/sdfsdfsdf”

@alexisvincent oh of course

I just used the "raw" cljs.build.api and get no erros. I think that it's a #figwheel problem

do you have the latest figwheel?

Yeah… but Im still getting errors. I cant import React Router. Keep getting errors

maybe not latest

@alexisvincent you could also check out lein with-profile cljsbuild deps :tree and look at conflicts

or lein with-profile figwheel deps :tree etc.

issues log in figwheel clearly shows someone requested this in a feature request issue, and the issue was closed marking as implemented

as of late june

hmm thanks. Thats helpful

It looks like it was an error with rum. Since React Router assumes a react instance and rum includes its own one

got a little bit further

ahh that sounds like something that could cause that issue

but hit something else now

Hey friends, I'm investigating compiling clojurescript with macros - is it possible to define a macro that exports a function to js-land via ^:export metadata in a macro? Best I have for it right now is (defn (with-meta ~(symbol fn-name) :export) [] ...) since I hear reader macros are no good in macros.

nm sorry, I clearly didn't read defn specs closely enough - for anyone else wondering, (defn ~(symbol fn-name) {:export true} [] ...) did the trick just fine.

question guys: what is your choice of charts library to work with a frontend in reagent ?

Guys, How is that possible with production build with npm modules ? I can use it with dev profile, Clojurescript can find this module and add for me. But it comes to production build. It can’t.

It is obvious too ?

@scknkkrer you're probably missing externs

Nope, cljsbuild npm-deps feature only works with optimization is none profile.

But thanks for asking @dabra.

oh, yeah you need to add :npm-deps to all builds

Yeah, my problem was, I just want to get optimized out from project. When I build min version of my project it gives error because npm-deps feature doesn’t work with advanced optimization profile option.

It’s a good trick.

Does anyone know how to use normal React components nicely in rum. Without resorting to react/createElement nonsense

Hey, does anyone know why cljs has put! but doesn't have take!?

derpocious: in core.async? It has: https://github.com/clojure/core.async/blob/master/src/main/clojure/cljs/core/async.cljs#L90-L103

@the-kenny thanks, do you know why this prints for <! but not for take!?

http://app.klipse.tech/?cljs_in=(ns%20demo.core%0A%20%20(%3Arequire-macros%20%5Bcljs.core.async.macros%20%3Arefer%20%5Bgo%20go-loop%5D%5D)%0A%20%20(%3Arequire%20%5Bgoog.dom%20%3Aas%20dom%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%5Bgoog.events%20%3Aas%20events%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%5Bcljs.core.async%20%3Arefer%20%5Bput!%20chan%20%3C!%20%3E!%20timeout%20close!%20take!%5D%5D))%0A%0A(def%20a-channel%20(chan%202))%0A%0A%0A(go%0A%20%20(%3E!%20a-channel%20%22Hello%2C%20wworld!%22)%0A%0A%20%20%3B%3B(println%20(%3C!%20a-channel))%0A%20%20(println%20(take!%20a-channel))%0A%20%20)

derpocious: check the documentation for take!. In Javascript world you can't do blocking stuff at all, so you need to supply a function take! will call when a value arrives on the channel

thanks. this might be dumb question, but is there documentation for cljs core.async?

besides the source itself

I was looking for it here: http://cljs.github.io/api/cljs.core/

Also, in the source for <! all it does is throw an error? that doesn't seem right

(defn <!
  "takes a val from port. Must be called inside a (go ...) block. Will
  return nil if closed. Will park if nothing is available.
  Returns true unless port is already closed"
  [port]
  (throw (js/Error. "<! used not in (go ...) block")))

@derpocious the go macro rewrites the code inside (<! ...)

the function body is only there for if you call it outside of a go block

ah ok thanks

is there a difference between "port" and "channel"?

the source for the cljs version of core.async is wildly complicated

the go macro is probably the most complicated macro I've ever seen

@derpocious a channel implements WritePort and ReadPort

@souenzzo just in case you haven't figured this out, the answer to your problem is that you can't used quoted symbols in a leinigen profile

just take the quotes off and you will be all set

@derpocious Your code should instead look like

(go
   (>! a-channel "Hello, wworld!"))

(take! a-channel println)

hey @mfikes ... I was just trying to understand a post you made a few years back: <https://groups.google.com/forum/#!topic/clojure/34luqPyg6L4>

I'm trying to export a lib from CLJS to JS and require the JS side to see "normal" looking functions

it sounded like this was what you wanted too, but perhaps I misread.

(As an aside, FWIW, the ^:export stuff on protocols is now mentioned officially at https://clojurescript.org/reference/advanced-compilation#access-from-javascript)

Yes, @hagmonk if you use ^:export, this makes it possible for JavaScript to make calls into your code when :advanced is applied.

I'm using optimization: whitespace right now for a couple of reasons, but on the JS side even with ^:export I still see myns$module$IDatasource$testDataSource$arity$1()

rather than myns.module.testDataSource

Well, ^:export doesn't change your code. It only adds additional aliases that point into your optimized code. But it is interesting that you are running into this under :whitespace because in that case ^:export is not needed at all. Your functions should be available in unaltered form.

@hagmonk thats how protocols looks. if you want actual JS functions you need to define the functions on Object

ah, I think I'm misunderstanding what :export is supposed to provide ... really it's just "don't munge"?

(deftype Thing [] Object (^:export foo [this] ....))

@hagmonk I need to run. But that Google groups post describes stuff that is open source. You can take a look for yourself how I did it: https://github.com/mfikes/goby

Cool, I'll pick this up again later, I also have to run. thanks @mfikes and @thheller!

@hagmonk FWIW, if you define the example protocol on the ClojureScript site:

(defprotocol IFoo
  (^:export bar [this])
  (baz [this x])
  (^:export quux [this x y]))

@hagmonk Furthermore:

cljs.user=> (defrecord Foo [] IFoo (bar [this] 1))
cljs.user/Foo
cljs.user=> (def f (->Foo))
#'cljs.user/f
cljs.user=> (js* "cljs.user.bar(cljs.user.f)")
1

@mfikes myns$module$IDatasource$testDataSource$arity$1() is the property on the actual object, not the dispatch fn. so I think he was looking to export a propery that external JS can call.

ie. f.bar() which doesn’t exist since its a protocol not a normal fn

@thheller Could be. @hagmonk initially referred to a question I had asked and then answered, and that question was about exporting functions defined by protocols.

yep, I think its just a misunderstanding regarding how protocols work

IMHO @hagmonk will have to clarify the question

(Honestly, my difficulty with these kinds of questions is that I don't know JS.)

I think you are right, though @thheller in that @hagmonk referred to "normal" looking functions.

I know that he is looking to implement a grafana plugin which expects JS classes so I assumed so.