Hi, suppose I specify a clojurescript keyword as the first argument to history.pushState and want to deserialize it back into a keyword in my popstate handler. How would I go about doing so?

i.e., short of doing: (keyword (.. % -state -name)) (which is kind of cheating)

@johanatan: in general, I’d probably use pr-str and read-string

(js/history.pushState #js {:state (pr-str data)}) and then (set! js/onpopstate (fn [e] (let [data (read-string (aget event “state” “state"))])))

i wouldn’t call it cheating, just necessary interop that you just write once

there is an issue in current CLJS regarding generating functions from specs, ex: (clojure.test.check.generators/sample (s/gen (s/fspec :args (s/cat) :ret int?))) this code works on Clojure, but errors on Clojurescript: #object[TypeError TypeError: Cannot read property 'for_all_STAR_' of undefined]

There is a test function in clojurescript: https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L10339

How do I use it?

This is the code of test:

(defn test
  "test [v] finds fn at key :test in var metadata and calls it,
  presuming failure will throw exception"
  [v]
  (let [f (.-cljs$lang$test v)]
    (if f
      (do (f) :ok)
      :no-test)))

How do I set the code of the test into (.-cljs$lang$test v)?

@viebel See the first example at https://clojuredocs.org/clojure.core/test

In short :test metadata

I know

But it doesn’t work

cljs.user=>(defn my-function "test" {:test #(assert false)} ([]))
cljs.user=> (test #'my-function)
:no-test

I ran it in a fresh repl with java -jar cljs.jar -m cljs.repl.node

I also tried in planck and in klipse

getting :no-test

😞

What’s the meaning of (.-cljs$lang$test v)? It is a javascript key, right?

@viebel It appears deftest does the right thing, but perhaps work needs to be done to make :test work

@viebel Interestingly, this appears to work:

(defn my-test
   [v]
   (let [f (:test (meta v))]
   (if f
    (do (f) :ok)
    :no-test)))

Yeah. I noticed also.

Do you think I could submit a patch with it? Or it might break deftest?

BTW, this is the implementation in clojure: https://github.com/clojure/clojure/blob/clojure-1.8.0/src/clj/clojure/core.clj#L4647

the CLJS implementation might have to do with the fact that you can’t add metadata to vars at runtime

hence the cljs$lang$test

@mfikes @viebel ^

Perhaps the :test path is just a matter of properly hooking up .-cljs$lang$test

I discovered something: with java -jar cljs.jar -m cljs.repl.node the following works:

cljs.user=> (defn my-function "test" {:test #(assert true)} ([]))
#'cljs.user/my-function
cljs.user=> (test my-function)
:ok: 

but this one doesn’t:

cljs.user=> (test #'my-function)
:no-test

But in planck and klipse both don’t work => :no-test

@viebel @mfikes this conversation is better suited for #cljs-dev

@wilkerlucio hrm, just seems like you haven’t loaded the test.check namespaces, if that isn’t true then file an issue

I'm wondering what do you folks use for your non-cljs build pipelines. Gulp? SASS? Postcss? Webpack? Assets story feels a bit neglected in CLJS-related posts so it would be nice to hear your stories :)

@si14 There are Less and Sass plugins both for Boot and Lein, e.g. https://github.com/Deraen/less4clj https://github.com/Deraen/sass4clj

@juhoteperi thanks! However, if I want to add e.g. autoprefixer + postcss-flexbugs-fixes to the mix, it becomes somewhat more complicated :) Same with image compressing

@dnolen you are right, requiring more namespaces fixed the issue, thanks

@juhoteperi: It's hacky, but I always fall back to this in a pinch - https://github.com/hyPiRion/lein-shell

@wilkerlucio Clojure can automatically loads those namespaces we cannot - we have some code to give a hint what went wrong but it probably needs more work

@juhoteperi : Similarly, if you want to make sure stuff is installed before you try to run shell commands, I use lein-npm : https://github.com/RyanMcG/lein-npm

^ @si14

hey all. How can I make a file with defs that can be read in both cljs and clj?

googlign around seems to suggest I should use reader conditionals and a cljc file

@nickt Reader conditionals: http://clojure.org/reference/reader#The%20Reader--Reader%20Conditionals

but my defs are just constant strings and numbers... I don't really need to differentiate between clj and cljs

Yeah if you want to cross-compile, you still have to use cljc

@nickt that’s what cljc is for

you don’t need reader conditionals for many things

You don't have to use the conditional to use cljc

especially now with automatically aliasing of typical core namespaces

ok so if I just make a cljc file with a couple def statements I should be able to require it in both clj and cljs?

@nickt not quite, CLJS doesn’t support namespace-less files yet

so you need at least an ns form

@dnolen clojure supports .clj files without namespaces?

@tmtwd yes

didn’t even know that, although that makes sense as project.clj doesn’t have ns nor does build.boot

on the list of things to enhance in ClojureScript, it’s just trickier

I thought that each namespace became a java class at compilation, so it was necessary somehow

Yeah I've only ever used it for one-off scripts. clojure uses that feature internally for things iirc

@tmtwd well there is the implicit user ns so I should probably qualify here

ah I see, interesting

hm ok... completely unrelated question: Is there an option I can pass to cljs.build.api/build that disables caching? Always rebuilds completely?

also, I made a file called constants.cljc with an ns form (ns iss.constants)

from my macros.clj file I tried (ns-resolve 'iss.constants blah) and it tells me "no namespace iss.constants found"

ahhh yes I figured it out, nvm 🙂

@xcthulhu @juhoteperi thank you (again) :)

Hey, quick follow up to my previous question... if there's no way to disable the cache in cljsbuild, is there a way to manually clear it?

@nickt :cache-analysis false should work if that’s what you’re talking about

if you’re talking about writing out the cached compiled stuff, no

you just need to delete the output directory

ah that makes sense!

thanks