This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-11
Channels
- # admin-announcements (10)
- # arachne (2)
- # beginners (74)
- # boot (302)
- # cider (49)
- # cljs-dev (11)
- # cljs-edn (7)
- # cljsjs (13)
- # cljsrn (1)
- # clojure (164)
- # clojure-austin (1)
- # clojure-brasil (3)
- # clojure-finland (2)
- # clojure-greece (4)
- # clojure-russia (48)
- # clojure-uk (11)
- # clojurescript (138)
- # community-development (1)
- # cursive (13)
- # datascript (1)
- # datomic (19)
- # emacs (4)
- # events (1)
- # garden (1)
- # hoplon (123)
- # jobs-discuss (9)
- # keechma (5)
- # lein-figwheel (4)
- # leiningen (2)
- # luminus (15)
- # mount (1)
- # off-topic (8)
- # om (66)
- # on (1)
- # onyx (28)
- # other-languages (2)
- # planck (1)
- # proton (5)
- # re-frame (18)
- # reagent (15)
- # untangled (15)
moving the migrations to the resource path so they are emitted as final artifacts fixed the issue
@kenbier They couldn't be in in the src directory without triggering that error?
@mahinshaw just implemented untangled websockets and made a cookbook, check it out: https://github.com/untangled-web/untangled-cookbook/tree/master/recipes/websockets
@ethangracer: unforunately i believe boot does not allow overlap between src and resource directories.
:source-paths #{"src/client" "src/server" "src/shared" "scss"
"test/server" "test/client" "vendor/src"}
:resource-paths #{"resources" "src/server/adstage-report-center/migrations”}
huh, I haven’t played much with boot so not familiar with its needs
clojure.lang.ExceptionInfo: Assert failed: The :source-paths, :resource-paths, and :asset-paths must not overlap.
(empty? (set/intersection paths parents))
@ethangracer: This cookbook/untangled-websockets looks pretty awesome - excited to try it out in our project. Seems like it's the case, but just to clarify - with this setup all reads/mutations go over the websocket? Seems like the client example overrides networking completely, but I don't know the details of the untangled client well enough to be sure.
that’d be a question for @mahinshaw — he wrote it! It does look to me like everything goes over the websocket if the mutation has a non-falsey value for the :remote
keyword
Ah, I guess also thanks @mahinshaw !
@therabidbanana: Welcome. Yes the entire client network gets overriden, and all mutations and reads go over websocket.
That seems to make sense to me - we'll try it out and see how it works for us. Excited for push notifications because currently we've got a thread that blocks a certain read until work happens on the server and saves to the database.