Fork me on GitHub

@mikethompson why you are suggesting here to use synthetic namespaces (what is rationale)?


I did a lein new re-frame yada yada and haven’t really changed anything in configuration; but when I lein cljsbuild once min & deploy to my S3 bucket, it’s still trying to do the figwheel connection stuff


is that not disabled when you do a min cljsbuild?


:figwheel true isn’t present in my min build info… nor in my dev one, for that matter :^


@samueldev can you copy the console printout? My guess is a forgotten lein clean


@dragoncube: not sure why other people use them, but I use them to keep things organized - your events, subs, fx etc. aren't automatically namespaced, so it's as much advice to namespace things as it is to use synthetic namespaces specifically - it just gives you the option to call it whatever you want.


all I’ve got is the typical browser output on failed figwheel ws connection


`Figwheel: trying to open cljs reload socket VM333:35 WebSocket connection to '<ws://localhost:3449/figwheel-ws/dev>' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED`


gonna try a lein clean


which’d be a classic mistake :X


oh woops, i meant to say terminal instead of console. so what is printing after you did lein cljsbuild once min


(i forget to clean all the time)


@shaun-mahood the question is mostly why synthetic, but not existing ones


ah, turns out I’ve got some bad things happening @gadfly361


I’m using :refer for those particular components


is that a no-no when doing min builds? do I need to qualify the namespace?


(trying anyway)


hmm just looking at the first error, i would say the namespace itself may be misnamed ... dev builds are forgiving when a namespace is misnamed, but min builds arent


is it the same as I’d expect in clojure? (ns chalk.components.fact-blob) —> folder path chalk/components/fact_blob?


a thing that often can happen is the file is called chalk/components/fact_blob and the namespace is named chalk.components.fact_blob ... when it should be chalk.components.fact-blob ... i.e. _ to -


yeah, same as clojure


so my second guess is there is a typo somewhere, may not be an underscore to dash thing since you are aware of that, just a spelling error or something.


@dragoncube: Ahh, synthetic namespaces is mainly a choice of what works for your code - if your full namespaced event is something like then you can just call it :common/make-cube - totally there if you need it, but if not then you don't have to worry about it.


ah yeah, I think it’s that I've got components in their own folder… so it expects a file called fact_blob.cljs under chalk/components/, when it is in fact under chalk/components/fact_blob/


yep that was it. additionally, uploaded to s3 and no longer seeing original figwheel issues 🙂


I totally thought it was going to be some crazy lein template thing :) I just turn on the gadfly signal for those ones.


smh, I’ve written a monolithic re-frame app over the course of 2 months and am almost done (hence finally getting it up in s3)


and am only now realizing that this is valid for classes on hiccup: [:div.class1.class2]


my entire codebase is [:div {:class “class1 class2”}] ><


well at least you only missed out on a little bit of sugar 😉 Sometimes I find myself writing it the long way tho ... i like my editor's syntax highlighting to bring attention to what classes i am using


@shaun-mahood you can require namespace and alias it something shorter, the only advantage I see is that you are not introducing dependency, though in some situations it could become disadvantage (ex. advanced compilation)


@dragoncube: I might be missing something, but when you register your events with reg-event-fx :ns/id I'm not sure how your aliased namespace in the cljs file matters - are we talking about the same thing?




(reg-event-fx ::my-event)

  (:require [ :as nav-menu-events]))

(dispatch [:nav-menu-events/my-event])


Note: in the #jobs channel, Oracle is advertising a reagent/re-frame position


@dragoncube: does that work? I've never tried it. If you used a synthetic namespace there, you wouldn't have to require the specific events file in your views file.


@shaun-mahood yep, we use it in our codebase


To my understanding you are talking about the difference between these options


(reg-event-fx ::my-event)

  (:require [ :as nav-menu-events]))

(dispatch [:nav-menu-events/my-event])


(reg-event-fx :nav-menu-event/my-event)


(dispatch [:nav-menu-events/my-event])


I would say 1 is more reliable, but brings in the dependency ... so yeah, matter of preference. I prefer ::


When I register things, like events, I want to provide an id. A nice unique, meaningful id, which conveys meaning. The fact that I use a keyword, or a namespaced keyword or a synthetic namespaced keyword is, to me, not that important.


@gadfly361: yep. The problem I have with option 1 is that the dependency isn't otherwise required, so you're adding a lot of dependencies across your program that are otherwise unnecessary. Purely a matter of preference and what makes sense for your project, though. Thanks for showing me something I didn't know @dragoncube, I didn't even realize that doing it that way was possible.


in the doc I mentioned, specifically synthetic is bolded, that why I’m wondering why


@dragoncube: probably a good idea to add a bit of discussion about the 2 approaches in there


@dragoncube we've had a lot of questions over a period of time on this (how to organise bigger programs). So we give that advice. In the interests of clarity and the id being meaningful, I prefer a keyword using a simple, synthetic namespace, rather than a much longer true namespace which is harder to scan.


re-frame is awesome, even Oracle choose to use it.


But YMMV. You can use strings if you want :-)


You can even do:

   [12 "hello I'm a teapot"]
   (fn [db v] .... ))


providing that you later do this: (dispatch [[12 "hello I'm a teapot"] :other :params])


Hi, I use the re-frame-template and put

(defmacro log [& args]
  `(do (.log js/console ~@args) nil))
in core.clj and (:require-macros [fcc-voting.core :refer [log]]) in events.cljs and it works well in one demo proj. But when I do the same thing in another demo , it shows
Compile Exception 
java.lang.AssertionError: Assert failed: Circular dependency detected, -> fcc-voting.core -> -> fcc-voting.core (not (some #{ns-name} seen))
. I wonder why the circular dependency happens and try to understand why should the template maintains both a clj folder and a cljs folder?. I found the following descriptions in the book Learning Clojurescript, is the reason have something related to this?
The fact that eval isn't available to the current ClojureScript runtime has direct implications for how macros work in ClojureScript as well. Since eval is only available to the JVM Clojure process, ClojureScript macros are also only able to be evaluated at compile time, rather than at run time, and they must be written in either a .clj (normal Clojure) file or a .cljc (reader conditional Clojure) file. Either way, code that is generated by a macro must target the runtime capabilities of ClojureScript, even if the macro itself is written in Clojure. In practice, this also means that ClojureScript macros need to be evaluated before we get around to actually calling them anywhere. The most common way of achieving this is to define them in another namespace than the one in which they are going to be called. They are then imported into the calling namespace using the special :require-macros keyword in namespace declarations, for instance:
       (ns my.namespace
         (:require-macros [my.macros :as my]))
A ClojureScript namespace can require macros from a namespace with the same name (that is, a my/namespace.cljs file could require macros from a my/namespace.clj file). There's one gotcha to be aware of with this—an imported macro and a function can share the same name. If that happens, ClojureScript will resolve the symbol to a macro if it's in a calling position, and to a function if it's not. 
Am I described my question clearly? Thanks.


It seems that is because of I required [fcc-voting.core :refer [uuid]] this line prompts the circular dependency error.


@mikethompson ok, so, it is mostly readability of shorter names, right?


Hi, what is the recommended way of adding css styles to component in re-frame? inline or use garden/less/sass?


I used

(defn polls-list []
  (let [polls @(re-frame/subscribe [:polls])]
    (.log js/console polls)
     (for [poll polls
           :let [title (:title poll)
                 id (:id poll)
                 k (str title id)]]
       ^{:key k}
       [:a {:href (str "#/polls/" id)
            :style {
                    :height "40px"
                    :width "100%"
                    :background-color "#fff"
                    :border "1px solid #ddd"
                    :margin-top "-1px"
                    :display "block"
                    :line-height "40px"
                    :border-radius "2px"
                    :color "inherit"
                     :background-color "#f00"
                     :text-decoration "none"
but the pseudo class hover does not work.


I found the hiccup way

             {:font-weight 'normal
              :text-decoration 'none}
              {:font-weight 'bold
               :text-decoration 'underline}]]
does not work inline either.


@cmal i personally use garden


@gadfly361 Thanks. Do you know how to insert <br/> in hiccup code? I've insert <br/> into hiccup code but it is escaped by default.


@cmal hmm not sure i follow, but is this what you are after?

[:div {:dangerouslySetInnerHTML {:__html "<br/>"}}]


@gadfly361 Thanks. I've been searching for this for hours.


Does this [:div I used in re-frame is actually hiccup? So I can safely require hiccup.core in my views.cljs to do extra works?


It's hiccup-based syntax, it compiles to a JS virtual dom so no.


@cmal: Regarding styles, I prefer just using a css processor like less, sass, or stylus


I sometimes have the style file in the same folder as the component for convenience


@curlyfry Do you know some articles for doing that?


personally I use garden for my styles because... clojure! 🙂


and I'm already writing my HTML in hiccup syntax, might as well do CSS in it too


If it can import some css to use in component, I will not need to rewrite quite a lot of the css now.


@cmal There's really nothing special about it, I just use classes like in any other html project!


@akiroz see. I also write some css in garden. But I think it is also a good idea to write css in views. For now, jsx is doing inline css too. It show a trending to do component work for frontend.


Or if you mean dividing it up into different files, it's a bit different for different preprocessors


Usually you have some form of "main" style file that imports the rest


Ok. I think for now I will still use less/sass. It's ok and will not cause much re-write works.


@cmal I've done inline styles in another project that uses a React/RadiumCSS stack it was pretty messy, I'd perfer to have a seperate css file for pages. I guess inline styles might work better for self-contained components


Thanks for your guys' opinions.


@dragoncube yep, readability. It is just an id


  "Returns a Reagent/reaction which contains a computation"
That is, `make-reaction` here provides precisely none of the
  benefits of `reagent.ratom/make-reaction` (which only invokes its function if
  the reactions that the function derefs have changed value).


@shaun-mahood: was there a technical problem with recording your Conj talk? It isn't posted with the others on ClojureTV


It seems to be missing from the playlist of conj2016


Good that it's there. With the live coding you really need the video to follow along. I'll let Alex know.


Cool would be nice to ping alex indeed


@wasser: thanks for catching that!


Only good thing to come out of writing a trip report to get my expenses paid. Need to be thorough. I DM'd Alex over on #clojure-conj


Just heard from @alexmiller - all fixed.


@cmal: You can also do [:br] in hiccup


What's the reason that we don't expose a version of dispatch and subscribe that wraps the internal state of re-frame?


(namely re-frame.db/app-db)


not sure about dispatch but I think it'll be nice if there's a built-in sub for app-db because I use it in my signal graph sometimes so I need to write my own (reg-sub :app-db identity)


@escherize can you expand on that? Don't quite understand the question


@akiroz it's highly unlikely we'll provide an :app-db sub or similar, the idea of subscriptions is to get away from you having to couple your application state to your views


In practice it is common for people to make subscriptions to subtree's of a view for a certain section. But I wouldn't recommend a subscription to the root


Also, it will not be particularly efficient, as that subscription will rerun itself any time anything in app-db changes. Most of the time of course there will be no change in data, so the data flow will stop there, but you still have a reaction running on every change


@danielcompton: I think I might have confused myself on something with subscriptions during my talk prep, can you clarify something for me? If I have an app-db {:a [1 2] :b [3 4]}, and subscriptions (reg-sub :a (fn [db _] (:a db))) (reg-sub :b (fn [db _] (:b db))) (reg-sub :all (fn [db _] db)) Assuming I have a view that uses all 3 subscriptions, which subscriptions will re-run if I change the value of the app-db to {:a [1 2 3] :b [3 4]}? Is sub :b able to tell that the value it depends on hasn't changed automatically, or does it have to run its query function (:b db) and check the value to figure that out?


All of them will run


If the input changes, then the sub will run


In all 3 cases, db is changing so the sub runs it's fn


However in a well architected re-frame app, you would usually have a handful of subscriptions corresponding to major sections of your app-db, and then create subscriptions off of that for use in your views


That way, you minimise the number of subscriptions that need to run, and build a more elegant signal graph


To be clear, there's a few phases involved here: 1. subscription data source changes 2. leads to subscription rerunning (always) 3. That may lead to the data returned by the subscription changing. 4. Which would then trigger further subscription updates and eventually a change in the view if view data changed


Ok good, my understanding was correct and I didn't misinform everyone at the Conj 🙂


4. Which would then trigger further subscription -where should be these further subscribtions?


i know about reaction on subscription


@andre other reg-subs which use :a and :b as inputs


rather than taking a db directly


sorry. how can i reg-sub using ;a as input?


reg-sub has only a db as input, no?


i should read the docs again 😉


i found There's 3 ways this function can be called


i know only one 🙂


@andre read You could do this:

   (fn [_ _] 
        (subscribe [:a]))
   (fn [a v] 
OR, using the syntactic sugar, this:
   :<- [:a]
   (fn [a v]