Re: :npm-deps and transitive dependencies

2018-01-16 Thread Lucas Wiener
I now realise that this question might belong to the ClojureScript group, so I'm posting it there as well. Feel free to remove this thread if you want. Den måndag 15 januari 2018 kl. 09:01:55 UTC+1 skrev Lucas Wiener: > > Hi, > > I have the following clojurescript project depende

:npm-deps and transitive dependencies

2018-01-15 Thread Lucas Wiener
Hi, I have the following clojurescript project dependency setup: X -> Y (X has stated Y in :dependencies). Now, I would like Y to depend on a npm javascript library Z. Following the guides, I added :npm-deps to one of the builds specified in Y. When I build and run Y, everything works fine

Re: Spec - is there any way to tell which keys are not described by a spec?

2018-01-14 Thread Lucas Wiener
ent in the data but not in the > spec. I'm going to try to make some kind of gist with functions that does > this, surely the resources you linked to will be helpful as a base for that. Den fredag 5 januari 2018 kl. 23:16:11 UTC+1 skrev Lucas Wiener: > > Ah, yes that seems to be wha

Re: Spec - is there any way to tell which keys are not described by a spec?

2018-01-05 Thread Lucas Wiener
brary, too. It’s not > exactly what you were asking for, but I think it could help you quickly > create (rough, approximate) specs that incorporate all witnessed keys. > > On Friday, January 5, 2018 at 11:49:15 AM UTC-5, Lucas Wiener wrote: >> >> Hi, >> >>

Spec - is there any way to tell which keys are not described by a spec?

2018-01-05 Thread Lucas Wiener
k it would be useful to have something that tells me "keys :x, :y, :z are not in the spec" or "the spec describes a subset of the given data". Is this possible? Kind Regards Lucas Wiener -- You received this message because you are subscribed to the Google Groups "Clojure&

(doseq/lazy/interop)? problem, different behaviour when adding a println

2017-04-22 Thread Lucas Wiener
Hi all, I'm working on solving the problem http://adventofcode.com/2016/day/11 , and ran into some weird behaviour. I have solved the actual problem, so let's not focus on it. Here's my code: (defn compute3 {:test (fn [] (is= (compute3 (create-state "F4 . . . . . "