oh ok @maria, did not know that, maybe I missed the place where it is written ..

in any case

thanks for solving, i was banging my head on the floor 😄

howdy.

anyone around who can give me some pointers around cljs.test

I setup some simple "hello world" style deftest's last night and I was able to run them successfully using cljs.test/run-tests

now though it doesn't seem to be able to locate them

I'm doing an in-ns just prior to running run-tests

(all from clojurescript repl running with figwheel)

Are there any best practices in how to shape returns from an API? right now I’m doing {:status :success :other-data blah-blah} or {:status :some-sort-of-failure :other-data blah-blah}

@sander: https://gist.github.com/anonymous/0d5a1d91eec268673b49

@sander: so, running java -cp cljs.jar:src clojure.main repl.clj, will result in java.lang.RuntimeException: No such var: cljs.build.api/build

@maria: is the reason that :main causes the foreign libs not to be included that a file that's not loaded by main does not transitively require the foreign lib? Somehow the example repo doesn't seem to require jqconsole anywhere

@martinklepsch: I believe it’s a bug in ClojureScript. When using the :main option in combination with :advanced or :simple, instead of returning an IJavaScript map of the compiled file, the compiler returns a String which doesn’t have a goog.require for the foreign library. Will try to create the ticket and the patch today and then let’s see what dnolen says 😉

Ah interesting thanks @maria :)

@maria part of me wants to talk you into building lein-cljsbuild on top of shadow-build, but are you even aware of its existence?

https://github.com/thheller/shadow-build

I suck at writing docs which is why I generally don't advertise it much

but pretty much all of the bugs or build problems talked about here do not exist in shadow-build

but it may have other issues 😉

I started it a while back to get closure modules

David kinda implemented them in cljs but is missing some stuff

and still doesn't work in :none

which is a big issue for me because I think :none should be as close as possible to :advanced as possible from the user side of things

@theller: No, I didn’t know shadow-build. Having a look now 😉

:main not working in :advanced is just another example of that not being the case in cljs 😞

best to try https://github.com/thheller/shadow-build-example

but I started rewriting some stuff last week to finally get a complete REPL going

but the general idea stays the same

@thheller: Have you thought about using Cljs public API instead of the implementation namespaces?

I like the idea to just use a Clojure script to build your project. Especially now that ClojureScript supports JavaScript transforms which require you to add your own transform function.

@juhoteperi: that won't work cause it is pretty much a reimplementation of cljs.closure

@maria yeah seems to be the latest trend in cljs/figwheel to create a scripts/thing.clj to run things

which was the basic idea behind shadow-build from day 1

my general opinion being that cljs.closure/build is not enough to drive complex builds since you cannot express all options in a hashmap

@maria your work on transforms is not supported in shadow-build yet because I do not have a proper example of a library where that should work

I never had a need for it so I didn't port it yet

@thheller: fair enough

but as I said, I suck at writing docs so I don't blame you if you'd rather stick with CLJS proper

@dimovich no idea, sorry. are you sure you're using exactly the same cljs.jar in windows and in ubuntu?

@steve do you mind posting an example repo? Remember that cljs.test/run-tests is a macro that takes namespaces, finds their test vars, compiles the tests, and then runs them. If you are in the REPL and somehow "delete" the namespace, then run-tests will find no vars inside.

anybody had problems here with figwheel failing to re-compile .cljc files?

does anyone use ClojureScript + Node for making outbound HTTP connections?

jreedmoore: yes

I'm trying to write something for AWS Lambda on top of https://github.com/nervous-systems/cljs-lambda that talks to a bunch of HTTP RESTy APIs

@sander do you just use the node libraries w/ bare JS interop? or are there any nice wrappers around those?

@jreedmoore: no experience with aws, but i like the node.js request library

https://github.com/request/request

that looks pretty full featured and awesome!

I have no idea what I'm doing, but any advice on how I can turn the callbacks in there into core.async channels?

@jreedmoore: there are probably different opinions but here is one example: http://www.lispcast.com/core-async-code-style

@jreedmoore: Here HTTP wrapper for CLJS around standard node http https://github.com/artemyarulin/koh/blob/master/src/koh/http.cljs#L5

I just cut 1.7.145 https://github.com/clojure/clojurescript/releases/tag/r1.7.145

before putting together a proper announce it’d be great if people could take a second to test it

might take a few minutes for it to hit Maven Central

it looks like it hit MC

Figwheel is reloading a cljc file, but faling due to an undefined function, but this function is called inside a #?(:clj …) block and the function is defined in a clj file. The Clojure side of things is working fine and if I restart figwheel, it’ll work fine, but not hot-code loading. Any ideas what’s going on?

probably a bug?

@dnolen: Everything looks good with 1.7.145 for me, no issues in a Reagent app running on Windows

great thanks!

I’m trying to get going with emacs and cider via spacemacs. When I try to send my buffer to cider in a clojurescript project, I get this error: No such var: clojure.core/require-macros . . . can anyone give me a nudge in the right direction?

@dnolen: I just tested a couple of applications with 1.7.145 with all I got (rhino, slimer, phantom, chrome, etc.) without problems

@jeremyraines: I'm not sure about this but I don't think cider supports clojurescript like that. It is probably trying to read your namespace as a clojure file and failing.

https://github.com/clojure-emacs/cider#clojurescript-limitations

oh, dang. Back to vim I guess

or — what are people’s workflows for repls and clojurescript with emacs? I was experimenting with making the switch because whenever people spell out their vim setups for clojure, usually someone says something along the lines of “emacs does all that, but better, and better repl integration"

people (meaning me) say that about clojure jvm. I use emacs + evil-mode

but it is not integrated at all with my clojurescript workflow, which is mostly terminal/browser based

I've been trying to use intellij + cursive but my machine can't really take 2 jvms so it crashes often when I ran tests/servers on the side

Just gonna drop this right here… https://potetm.github.io/2015/10/04/beginning-clojure-cursive.html

For clojure + vim ^^

I see. I want to do clojure jvm stuff as well, so I’ll check into non-integrated workflows for clojurescript

Man bensu that sucks about crashing… Cursive is IMO by far the best clojure editing experience

@potetm: I now, but that will most likely change if I get a new machine with more RAM.

I tried cursive for a couple months, it wasn’t really for me; maybe I didn’t put in enough effort into learning intellij, but it seemed difficult to customize

@jeremyraines: that’s interesting, I basically have all the customizations I ever had in Emacs and more

the only thing I miss is org-mode, and I still use Emacs for that

ClojureScript 1.7.145 is out! big thanks to everyone who contributed

Woohoo!

ok. I know my issue is probably lack of knowledge about the clojure / clojurescript repl in general. I’m coming from Ruby, where I’m very proficient with Pry, and am not there yet. I’ve spent time learning the language and (some minimal part of) the ecosystem, and now I’m trying to get procifient with the tooling and understand whya lisp repl is so superior (I don’t doubt that it is)

@jeremyraines: Ruby REPLs are not bad, they actually support reloading

however mostly programming via a REPL just wasn’t something I could ever do with Ruby

@jeremyraines: what I find superior is the REPL workflow combined with an expression oriented language.

@dnolen: the way to inform you of "Patch in need of revision" is to assign it to you?

TBH @dnolen my immediate goal is to use a setup where I can get the most out of the workshop this weekend. I think I’ll be exposed to a lot of cool techniques that I want to be able to incorporate immediately rather than abandon or translate to vim. I know that’s not the primary goal at all but I got jealous of Tims’ emacs-fu during the Arcadia workshop

I’m up and running enough with Cursive that I could probably use that

@jeremyraines: not sure if that's what you're looking for, but i found inf-clojure a lot easier to set up in emacs than cider

thanks, I’ll check that out too

@jeremyraines: we’ll probably recommend Cursive to cut down on environmental issues

anything else will be too much trouble and consume too much time

people who are very comfortable w/ Clojure can make do of course, but it won’t be recommended

👍

+1 for Cursive if you are just starting and are time constrained.

how do you all handle combining ring war with ‘components’ when the handlers need collaborators? At the moment I have my handlers pull out of the system map pulled in via a namespace - yuck. The problem is that ring war wants to access the (no-op) handler var….

@roberto +1 for Cursive regardless. +1 for Emacs + cider (+ prelude) though as well

yeah, I started with Cursive and switched to Emacs. But my motivation was because I really wanted to learn Emacs.

Cursive is great

I can’t live without helm (helm-ag and helm-occur just rock my world).

and avy as well

Anyone running tests from repl in their development flow? Can you share your work flow?

Mine stopped working... trying to figure out why?

(in-ns 'blah.core)

(run-tests)

@steve do you mind posting an example repo? Remember that cljs.test/run-tests is a macro that takes namespaces, finds their test vars, compiles the tests, and then runs them. If you are in the REPL and somehow "delete" the namespace, then run-tests will find no vars inside.

Om 1.0.0-alpha1 is out

https://github.com/omcljs/om/wiki#om-next

3 tutorials to play with at your leisure, feedback, and bug reports now welcome

there’ll be a slew of releases as we get things ironed out. Overall I’m very excited about the architecture. I’d say this puts Om another 20 odd months ahead of everyone else

haha concat "again"

Does anyone have any good, up to date instructions on how to integrate figwheel with ring? I've found some older ones but would like to get something current into the wiki.

@shaun-mahood: you mean using figwheel to host your ring handler?

Thanks @dnolen. Looks really interesting. Great work as usual.

once the various issues are ironed you will have to pry Om Next from my cold dead heads, this is the UI tool I’ve been wanting for the last 10 years.

nice work @dnolen, can't wait to give it a try

Even with all the issues you identified with original Om, it has been a super useful tool and made developing UI's a pleasure. If Om Next proves to be half as good as you say then everybody else should pack up!!!! Which will be a shames as I've quite enjoyed playing with PureScript recently.

@keeds thanks!

@lfn3: I think I mean using ring to host figwheel, but I could be wrong. Essentially it would be what Chestnut does, I think. I've always had things split up in different projects up until now but want to start integrating the 2.

@shaun-mahood: Right. So afaik, figwheel will totally handle it’s own thing, independent of ring. See https://github.com/bhauman/lein-figwheel#scripting-figwheel

@dnolen: No problem. The thanks is all to you. Just converting a prototype I'm building to Om Next. Hopefully it will be enough to persuade a team of CoffeeScript/Backbone devs to switch to ClojureScript/Om Next!??!

You can just put something like that snippet somewhere downstream from your servers init method

@lfn3: Ok that kind of explains what that whole section was for. I'll see what I can figure out, thanks.

Good luck!

When using a CLJC file, am I wrong in assuming there are intermediate .clj or .cljs sources generated at some point that I could inspect?

i’m trying to work out why a macro is generating what appears to be the wrong code and I really want to see the .cljs source to see what the #?(:cljs …) has emitted

but i’ve been over my project folder and they don’t seem to appear there

you are wrong 😞 I think this is handled by the reader which just selects the appropriate part without generating an intermediate file

hrmm… darn

thanks bensu

in any case, you should be able to macroexpand whatever you are producing

i can, and the code is wrong

what’s not clear to me is why it’s wrong

ah, i wonder if this is about macros being clojure not clojurescript

just in case: remember that macro expansion is done in clojure jvm so it would pick up #?(:clj ...)

yes!

hrnn

right, if you use the compiler from the jvm, all macros are clojure jvm code.

yes it just occurred to me that this might be why it’s emitted the ‘clj path

so… now i am unsure how to emit cljs compatible code from a macro

@mfikes to the rescue

look in this blog http://blog.fikesfarm.com/posts/2015-09-05-runtime-macroexpand.html

hrmm… but this means writing a special case macro

unless i misunderstand the message here

if i have to do that i can just write a CLJS compatible alternative macro

of course i would really rather not have to do that

ahh you want a macro that you can call from the jvm and js and that generates different code for each

yes

i have to work around a bug in cljs

so i need the macro to emit different code for each path

the pragmatic thing to do is probably just say fuck it and write defcomponent-cljs

@sandbags: this is not really a bug. cljc just doesn’t cover macros - was out of scope.

dnolen: not sure what you mean, i’m not referring to cljc not handling #?(:cljs) as a bug

(in the macro case)

@sandbags: I’m not sure what you mean

you can’t put macros in #?(:cljs ...)

dnolen: i’m working around a CLJS bug that means I need my macro to be different in the clj and cljs cases

and i lost track of macros being compile-time and, hence, clj only even in a cljs context

so the #?(…) construct in my macro is always evaluating the :clj case

but what is the actual bug?

maybe you can #? over the top form and have #?(:clj defmacro :cljs defmacro) -- sorry this wouldn't work unless you used bootstrapped

bug is a strong word, if there is a bug I want to know about that

dnolen: it’s a known bug

i can find the number if you’re interested but it’s something you know about already, came up last week

@sandbags: can you be more specific? known where?

dnolen: IIRC 1451

ah the qualified protocol method names

my first approach was to use #?(:clj component-key :cljs ~(symbol “component-key))

but of course this fails because the :cljs case is never taken

yep I know what you’re talking about now

i’m still quite inexperienced writing macros

it occurs to me to wonder if the :cljs path would work for :clj also

though working around this via macros is about as likely to be as much work as just submitting a patch

the number of people that think that route is harder and then try and are surprised it’s really straighforward …

submitting a patch? to clojurescript you mean?

yep

i think you overestimate my chances

I think you overestimate how complicated the ClojureScript compiler is 😄

possibly, possibly not but i’d also have to understand the problem and the context which frankly i don’t … i mean i can take a look but as someone who only has the odd hour or two a week to code these days, i’m not sure it’s something i can tackle

@sandbags: yeah the problem is very simple

we’re not calling name on the protocol method

that would drop the namespace part

i’m having a look at the CLJS source now

i have about 15 min before i have to hit the hay

i would like to get past this problem

I think you underestimate @dnolen's patience. He'll write the patch through slack through you if needed 😄

heh

if he can do that in <15 then i have underestimated him for the last time

hahaha I don't know if you've noticed but there were 2 releases today, I would never underestimate him

https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/core.cljc#L1425-L1431

you can ignore pretty much everything except the calls to set! around this section

we’re just bashing on the JS prototype.

https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/core.cljc#L1410-L1415

the pf argument is likely a problem

since it will be a namespaced thing

again the trick is just to drop this

okay this is odd, i checked out the clojurescript project on github but the source appears to be different

it may even be solveable by fixing only this https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/core.cljc#L1192-L1193

i think perhaps i am tired

I’ve updated the ticket http://dev.clojure.org/jira/browse/CLJS-1451?focusedCommentId=41354&amp;page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-41354

okay yes, tired, there it is

in general I would rather help people fix the real issues than have them resort to dirty hacks

then everybody wins

and I’m not the only person that knows how this stuff works

assuming i understood this code or what you are suggesting, how would i go about testing this?

https://github.com/clojure/clojurescript/wiki/Developers

bunch of info about that here

gotta run but happy to answers more question left here later.

okay, i might have to come back to this next time … 00:21 here and I suspect i’m just not compehending, thanks anyway for your help, also @bensu

@sandbags: If you don't have the time I'll start with it tomorrow working on it with @dnolen's pointers

@bensu: that’s kind of you, i’m about done tonight and no idea when i’ll get a chance to code again

but i have the code (not that I understand it) and I will check back

feel kind of daft for not realising sooner why my macro was expanding wrong … <sigh>

ah well, g'night

@bensu I started with this "lein new figwheel om-tut -- --om"

Then added this to the :require at the top [cljs.test :refer-macros [deftest is testing run-tests]]

of core.cljs

as well as this simple test (deftest test-numbers (is (= 1 1)))

Then thought running this "om-tut/core=> (cljs.test/run-tests `om-tut.core)"

or simply "om-tut/core=> (run-tests)"

on the "lein figwheel" cli would find them.

But run-tests doesn't seem to detect my deftest, why? (sorry folks for newbie question)