Fork me on GitHub
#devcards
<
2016-01-04
>
peeja16:01:45

I'm a little confused about the cards.html. Is there a way to keep that from becoming part of the production site?

adammiller19:01:04

@peeja: if you are using lein you could use the uberjar-exclusions i’d think

peeja19:01:53

I suppose that would work

spieden20:01:57

is anyone successfully using devcards with reagent 0.5.1? seems like they have an incompatible react version dep

adammiller21:01:49

@spieden: did you try it using whichever uses the latest version and just exclude it from the other? Or exclude if from both and add dependency in yourself.

spieden21:01:09

@adammiller: yes i’ve been trying that

spieden21:01:36

now i’m attempting to merge a project generated by the lein template (which works) into my own

spieden21:01:32

hmm, a lein clean eventually did it =\

spieden21:01:38

some bad state creeping in

peeja21:01:46

Is there a stable version of Om that works with Devcards?

peeja22:01:29

It looks to me like Devcards requires React 0.14, which isn't supported until Om 1.0.0's alphas

spieden22:01:57

@peeja i just hit the same issue with reagent — 0.14 not supported yet

spieden22:01:11

i’m trying just bumping it and seeing what happens 😓

peeja22:01:29

@spieden: I'm rolling back to 0.2.0, which is React 0.13

spieden22:01:46

i tried that and hit different problems, but that was before i tried lein clean

spieden22:01:32

working now for me too

spieden22:01:11

@peeja do you know any way to have an interactive devcard without ns level state in e.g. an atom?

peeja22:01:57

@spieden: You can give a card initial state and it'll pass it to you as an atom