This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-02
Channels
- # beginners (118)
- # boot (73)
- # cider (2)
- # cljs-dev (65)
- # cljsrn (18)
- # clojure (49)
- # clojure-argentina (4)
- # clojure-italy (19)
- # clojure-portugal (1)
- # clojure-russia (1)
- # clojure-spec (34)
- # clojure-uk (102)
- # clojurescript (202)
- # code-reviews (3)
- # core-async (5)
- # cursive (11)
- # datomic (25)
- # emacs (1)
- # graphql (22)
- # hoplon (6)
- # keechma (59)
- # leiningen (10)
- # luminus (31)
- # lumo (78)
- # off-topic (141)
- # om (32)
- # om-next (2)
- # onyx (6)
- # parinfer (55)
- # pedestal (3)
- # protorepl (3)
- # re-frame (8)
- # reagent (8)
- # ring-swagger (1)
- # rum (20)
- # specter (1)
- # sql (5)
- # test-check (11)
- # vim (13)
- # yada (7)
@donyorm looks like there might be some conflict from +boot
profile here:
(defn mount-components []
(let [content (js/document.getElementById "app")]
(while (.hasChildNodes content)
(.removeChild content (.-lastChild content)))
(.appendChild content (js/document.createTextNode "Welcome to gallery"))))
(defn init! []
(mount-components))
@yogthos sorry, what's happening? Does that snippet not appear when using the +boot
profile?
Not sure this sent, my app is being weird: >Sounds like you already know about this, but I forgot to open an issue, so I'll mention it here, tests seem to include a require from reageant even if the reagant profile isn't be used, and therefore the tests fail. I might be able to put a PR up with a fix in a bit.
I guess that could be useful. In a couple of months I'll be starting my gap year so my activity is going to drop, so no promises what I will be able to do, but I'll do what I can.
So I haven't really done much in maintaining open source projects with others, mostly just worked on my own. Do non-owner maintainers usually do work in their own fork then pull request (and approve it themselves), or do they do work in a clone of the main repository in their own branch?
i’ve isolated my earlier uberjar compile issues a bit further, managed to fix the uberjar compile but turns out the exception is related to starting immutant via mount, i’m following essentially the same as luminus pattern , i.e mount/defstate http-server in my core ns , that starts immutant with http/run on a config sourced from cprop , with a handler function defined to return my routes
at every stage it looks pretty much the same as luminus template , works fine in repl , fails as standalone jar
any other thoughts on when using mount / immutant how to bind the handler? really scratching my head on this one
sigh alas no a fresh luminus template is fine , so bit by bit i’ve been going through , tbh by now about the only differences left are versions of the libs involved , i’d adapted my own more recent immutant ns for example (using latest 2.1.9)
implemented same using integrant instead of mount , same exception , works fine with my older component based , might just have to give up at this point , no damn idea
That is the weirdest issue. I have no idea what to tell. Did you try just deleteing your maven repository and letting dependencies redownload? Just in case something weird got stuck in there