This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-29
Channels
- # beginners (1)
- # cider (7)
- # cljsrn (6)
- # clojars (3)
- # clojure (35)
- # clojure-nl (2)
- # clojure-spec (5)
- # clojure-uk (9)
- # clojurescript (18)
- # clojurex (1)
- # community-development (2)
- # cursive (27)
- # datomic (12)
- # duct (11)
- # emacs (5)
- # hoplon (5)
- # immutant (2)
- # leiningen (1)
- # luminus (15)
- # nyc (1)
- # om (9)
- # om-next (5)
- # onyx (55)
- # parinfer (1)
- # re-frame (3)
- # reagent (44)
- # reitit (11)
- # ring-swagger (4)
- # shadow-cljs (25)
- # videos (1)
is it ok to mix clj, cljs and cljc files under src/
or would it create problems (with tooling etc)
@stathissideris totally fine. only might cause a problem if you use CLJS without a :main
config. see https://code.thheller.com/blog/shadow-cljs/2018/02/08/problem-solved-source-paths.html
@thheller great, thanks!
@stathissideris mixing all three is going fine in https://github.com/robert-stuttaford/bridge so far 🙂
thanks, I think I’ll do the same because I dislike “heavy” directory trees
so I’m trying to convert a map to a JS obj, one level deep, that I am dynamically generating
e.g. #js (merge {:foo foo} props)
isn’t working, because it needs to be used with {}
directly. but clj->js
would convert all of my nested data into JS as well, which I don’t want.
you need to add a [goog.object :as gobject]
require.
Do you know good example of code re-frame vs om.next? The same task, but with 2 tools.
I didn’t use fulcro, but intuition says me it lost all power with REST API. Better use re-frame then. Am i right?
re-frame is generic enough to serve as a powerful way to develop complex behaviors based on events/cofx/fxs, even in the backend
it's not just "this useful thing we have that eases UI development", but "this mental model that allows us to construct complex applications"