This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-05
Channels
- # beginners (12)
- # calva (18)
- # cider (1)
- # cljs-dev (29)
- # clojure (97)
- # clojure-uk (18)
- # clojurescript (10)
- # clojureverse-ops (2)
- # cursive (7)
- # emacs (10)
- # fulcro (42)
- # graphql (36)
- # joker (1)
- # juxt (28)
- # mount (2)
- # other-languages (2)
- # pathom (1)
- # portkey (3)
- # re-frame (50)
- # shadow-cljs (42)
- # spacemacs (4)
- # sql (6)
- # yada (6)
Yada team, I followed your online documentation and went ahead with starting a new project based on edge. Now in the latest code example, seems like even resources are configured as components. Can you please point me to the right documentation for better understanding. Thanks in advance
@gdrte The current (unwritten) recommendation is that you create yada resources as their own components, this granularity allows you to more easily understand the dependencies of a resource. I have a WIP guide that should help clear this up, but it's not yet published. You can do everything in code though, and Edge works fine with that too!
so If I do everything in code, what about the edge.lib.prod which is starting the app from config.edn?