This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-29
Channels
- # architecture (2)
- # bangalore-clj (2)
- # beginners (177)
- # boot (1)
- # cider (36)
- # clara (15)
- # cljs-dev (30)
- # cljs-experience (6)
- # cljsrn (7)
- # clojure (94)
- # clojure-argentina (2)
- # clojure-brasil (1)
- # clojure-dusseldorf (6)
- # clojure-greece (1)
- # clojure-italy (18)
- # clojure-norway (4)
- # clojure-quebec (1)
- # clojure-russia (28)
- # clojure-sg (3)
- # clojure-spec (12)
- # clojure-turkiye (1)
- # clojure-uk (12)
- # clojurescript (169)
- # code-reviews (4)
- # community-development (2)
- # core-async (6)
- # core-matrix (6)
- # cursive (35)
- # datomic (18)
- # devcards (4)
- # euroclojure (1)
- # hoplon (2)
- # keechma (4)
- # klipse (2)
- # leiningen (1)
- # luminus (16)
- # mount (1)
- # off-topic (34)
- # om (31)
- # pedestal (6)
- # re-frame (14)
- # reagent (33)
- # specter (4)
- # uncomplicate (8)
- # unrepl (15)
- # untangled (24)
- # yada (25)
@jhund Really nice, thanks!
'Morning. A quick question. We are developing a project which has 1 backend (ring and compojure-api) and 3 different interfaces (re-frame). Now we would like to split this huge project (and the git repositories) in 4 different subprojects. Any advice or thought about how we should proceed?
mdallastella: Perhaps you might be willing to use Posh for background data sync
@mdallastella can you give a bit more context on how you release changes/develop code, e.t.c.? The monorepo vs. separate projects decision seems to me to be mostly about what fits the org structure best
Do you have one Leiningen defproject
for all three re-frame apps + the backend?
@danielcompton Exactly... I was wondering if it's possible to have different lein projects (one for each interface and one for the backend)
Yep, that is possible. You can use lein checkouts, or :source-paths "../other-project"
to depend on code from other projects (within the same repo)
Thanks @danielcompton, I'll look further into lein checkouts... My idea is to checkout the backend project on every interface project. Does it make sense?
Yeah it does. If they're all in one repo then source-paths might be a better fit. Whichever you choose, don't forget to lein install
your depended projects when you change your dependencies, checkouts only handle source level changes, not project.clj changes
Is there a way for a component to declare subscriptions for its children? For example if a child subscribes to ::subs/todos
(which depends on the user who’s todos we want to show) and a parent declares ::subs/local-user
as Bob based on it’s props, then all children that subscribe to ::subs/local-user
and descend from the Bob parent component will get it as a user and it doesn’t have to be passed through every component in the chain.
@denik you can pass values to child components to do that, sounds fine to me
@danielcompton of course, until you have a hundred components, that really don’t need that prop, other than to pass it to subscriptions. it makes things look very noisy
I don't really understand what you're asking sorry?