This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-14
Channels
- # beginners (183)
- # boot (6)
- # cider (106)
- # cljs-dev (17)
- # cljsjs (2)
- # cljsrn (2)
- # clojure (56)
- # clojure-italy (14)
- # clojure-nl (39)
- # clojure-spec (49)
- # clojure-uk (138)
- # clojurescript (197)
- # core-logic (37)
- # cursive (22)
- # datascript (5)
- # datomic (29)
- # devcards (18)
- # emacs (1)
- # events (8)
- # figwheel (1)
- # fulcro (59)
- # lein-figwheel (1)
- # leiningen (1)
- # off-topic (54)
- # onyx (3)
- # pedestal (1)
- # portkey (4)
- # re-frame (18)
- # reagent (5)
- # reitit (43)
- # ring (6)
- # ring-swagger (26)
- # shadow-cljs (42)
- # spacemacs (8)
- # specter (12)
- # sql (3)
- # tools-deps (21)
- # vim (18)
Is it possible to set up devcards with editable source? (in the browser with auto-reload)
i.e. toggle card source, edit, see realtime results
I seem to remember seeing something like this, but I haven't been able to find a search lead
Nope, I just see the title and mounted component
To be clear, I would like the source to be editable in the browser. It works from my editor.
Yeah, just wondering if someone already implemented it somehow.
Not all my tooling, just a basic text editor which can be saved to trigger a reload of just that piece of code.
I think it would be a nice way of writing tutorials that are interactive.
If each card was implemented in it's own namespace, I imagine it wouldn't be too hard to implement something like this?
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?
@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
Reconsidering, it might be enough to just display the code without it being editable. Just saves maintaining the real code and 'display' code separately
@bhauman #127 and #123 - although I guess 123 isn’t really about Reagent per-se