This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-04
Channels
- # admin-announcements (36)
- # beginners (54)
- # boot (74)
- # cider (14)
- # cljs-dev (91)
- # clojure (197)
- # clojure-austin (1)
- # clojure-conj (3)
- # clojure-india (5)
- # clojure-japan (3)
- # clojurescript (111)
- # core-logic (12)
- # cursive (6)
- # datascript (3)
- # datomic (16)
- # devcards (26)
- # events (1)
- # funcool (11)
- # hoplon (63)
- # jobs (2)
- # ldnclj (10)
- # lein-figwheel (6)
- # luminus (5)
- # nginx (7)
- # nyc (3)
- # off-topic (1)
- # om (148)
- # onyx (122)
- # portland-or (5)
- # re-frame (3)
- # reagent (25)
- # yada (15)
i’m trying to use it, but i’m getting lots of warnings like nav already refers to: mecha1.www.component.page/nav being replaced by: mecha1.www.component.page/navat line 31mecha1/www/component/page.cljs
if it’s only for dev, i was thinking maybe a :reload
option to the hoplon
task could stick in the requisite reload stuff into the page, which you could then leave out int the prod build
on-page-load
will only ever fire when boot-reload or other compatible reloader triggers the custom event
yeah, not a big deal, but having the task emit it allows you to elide the stuff entirely in prod, and also doesn’t require you to add extra stuff in your code. not a big deal either way, but more of a convenience thing i think
(as an aside, i fixed my reload issue - apparently it didn’t like me having elements named nav
and footer
, so i renamed them and the warnings went away. weird)
@esp1: i wonder if the nav/footer thing is related to the fact that dom nodes with IDs exist in JS as global vars
@alandipert: actually, those nodes don’t have ids. i just changed (defelem nav …)
to (defelem m1-nav …)
and the warnings disappeared. same story with footer
. ¯\(ツ)/¯
i think the problem is with hlisp functions
nav and footer are HTML5 elements
already defined in hoplon core