This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-06
Channels
- # architecture (25)
- # bangalore-clj (1)
- # beginners (21)
- # boot (45)
- # cljs-dev (38)
- # clojure (272)
- # clojure-austin (7)
- # clojure-finland (7)
- # clojure-france (3)
- # clojure-italy (7)
- # clojure-japan (1)
- # clojure-russia (13)
- # clojure-spec (36)
- # clojure-uk (31)
- # clojurescript (96)
- # core-async (15)
- # cursive (16)
- # datascript (3)
- # datomic (97)
- # emacs (107)
- # hoplon (16)
- # jobs (9)
- # keechma (1)
- # luminus (1)
- # off-topic (19)
- # om (39)
- # onyx (15)
- # pedestal (3)
- # planck (22)
- # protorepl (4)
- # re-frame (20)
- # reagent (3)
- # ring-swagger (25)
- # specter (26)
- # test-check (19)
- # testing (1)
- # untangled (381)
I'm just neurotic 🤓. I will see how far I can get w Javelin + FB.
Am I correct in assuming I can construct and visualize graphs off the denormalized data in Firebase? Can you query parent/child relationships in the Javelin cell graph?
Like creating a custom sub-graph from the dataflow that's going into the UI.
@micha I did indeed have to bump the Clojure version to 1.8.0 (when string/includes? was added). Updated the properties file and the build file.
Then had some problems with nrepl deps, so added that (not sure why that's required, but seems like it is).
Finally had an error on the tt
html element, so changed it to code
(just to replace with anything).
also reverted ring and ring-defaults to the latest stable (rather than beta versions)
I'd be happy to send a gist or patch to whomever maintains the hoplon-castra template. Not sure who that is.
@mudphone a PR would be great
@thedavidmeister will do. I'm assuming https://github.com/tailrecursion/hoplon-castra-template is the correct repo?
Hmm, looking at the current lein template, it takes the latest versions of a lot of the deps. If I hard code them, seems like it will eventually get out of date and not-fun.
seems like it would be better to lock down a template with hardcoded versions of things that work and update it occasionally than to blindly use the newest versions of things and break occasionally
@mudphone that's the one, PR would be great. Current way is terrible