This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-01
Channels
- # admin-announcements (3)
- # beginners (25)
- # boot (21)
- # cider (39)
- # cljs-dev (86)
- # cljsrn (20)
- # clojars (4)
- # clojure (70)
- # clojure-canada (1)
- # clojure-greece (101)
- # clojure-poland (16)
- # clojure-russia (35)
- # clojure-spec (202)
- # clojure-uk (24)
- # clojurescript (69)
- # cursive (23)
- # datomic (34)
- # devcards (7)
- # dirac (5)
- # editors (3)
- # emacs (6)
- # events (1)
- # hoplon (52)
- # instaparse (1)
- # jobs (4)
- # jvm (2)
- # lein-figwheel (2)
- # leiningen (10)
- # luminus (2)
- # mount (1)
- # off-topic (12)
- # om (55)
- # om-next (8)
- # onyx (19)
- # pedestal (4)
- # planck (1)
- # re-frame (27)
- # reagent (5)
- # remote-jobs (1)
- # spirituality-ethics (14)
- # tmp-json-parsing (6)
- # untangled (121)
- # yada (32)
Can I ask one more weird question here? When working from the luminus template with +cljs, there's some weird kind of routing magic that I don't understand. Suppose I create a new route in pure clojurescript with secretary and reagent, and don't create a corresponding route in the server-side. When I go to that URL in the browser, somehow it seems to get routed to the template home page before the compiled cljs kicks in and displays the correct page. But the route is never actually defined on the server-side anywhere I can find. So how does it know to load up the default home page, and then call the clojurescript bit via app.js on that template, without a server-side route defined? Shouldn't it just throw a 404 or something? Is there a "default html template" buried somewhere in this code that I can't find?