Fork me on GitHub
#devcards
<
2018-06-14
>
danielstockton12:06:07

Is it possible to set up devcards with editable source? (in the browser with auto-reload)

danielstockton12:06:50

i.e. toggle card source, edit, see realtime results

danielstockton12:06:27

I seem to remember seeing something like this, but I haven't been able to find a search lead

dpsutton13:06:43

I get this by default. Is this not your experience?

danielstockton13:06:38

Nope, I just see the title and mounted component

danielstockton13:06:47

To be clear, I would like the source to be editable in the browser. It works from my editor.

dpsutton13:06:00

Oh. That's a bigger feature request

danielstockton13:06:13

Yeah, just wondering if someone already implemented it somehow.

dpsutton13:06:17

You would want all your tooling in the browser?

danielstockton13:06:42

Not all my tooling, just a basic text editor which can be saved to trigger a reload of just that piece of code.

danielstockton13:06:29

I think it would be a nice way of writing tutorials that are interactive.

danielstockton13:06:31

If each card was implemented in it's own namespace, I imagine it wouldn't be too hard to implement something like this?

paytonrules13:06:48

What’s the status with devcards and the latest reagent? It looks like the answer is “don’t’ based on a couple PRs in the issues page. Do we just stay on Reagent 0.7?

bhauman15:06:20

which PR's are you speaking of?

bhauman15:06:30

@danielstockton for whats it's worth I really looked at this and feel that editing in an editor is a much better experience even for tutorials. But if what you want is something like an editable clojurescript example you could create a Klipse card

danielstockton15:06:08

Reconsidering, it might be enough to just display the code without it being editable. Just saves maintaining the real code and 'display' code separately

paytonrules15:06:07

@bhauman #127 and #123 - although I guess 123 isn’t really about Reagent per-se

bhauman15:06:33

Hmmm I will investigate