Fork me on GitHub
#devcards
<
2015-10-08
>
seantempesta12:10:30

Hey @bhauman. First off, thanks for creating figwheel and devcards (figwheel changed my life!). I’m trying to wrap my head around a few things w/r/t devcards though. The goal is to not have them running at the same time as your app?

bhauman12:10:24

Figwheel can run two builds at the same time. So you can work on devcards and you app at the same time

seantempesta12:10:00

But the state wouldn’t be shared?

bhauman12:10:06

Nope, but you can put your whole App in a card if you want to share state. But sharing state isn't the intent.

seantempesta12:10:50

I see. Is there a way to choose where devcards is rendered in the DOM?

bhauman13:10:58

@seantempesta: this isn't recommend, why do you ask? Is uses routing so even if it was co rendered with your app it probably wouldn't work out well. I take it you haven't tried it yet?

seantempesta13:10:05

Well, I was thinking I could render it in iframe to avoid the routing issues.

seantempesta13:10:53

The reason I want to do this, I’d love to have more insight into what’s going on in my app while it’s running. I’m using re-frame so being able to inspect the app-db ratom, rollback in time, etc. would be super useful.

bhauman13:10:27

@seantempesta: yeah that's a really different use case and a small set of functionality that you can get from ankha and snapshoting your state atom.

bhauman13:10:31

Devcards is not meant to be tooling for your main application, Unless you run your whole app inside devcards

seantempesta13:10:51

Okay. I’ll take a look at ankha. Thanks for your advice!

darwin21:10:41

@seantempesta: for inspecting your re-frame app-db you can use https://github.com/binaryage/cljs-devtools