This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-12
Channels
- # aws (21)
- # aws-lambda (8)
- # beginners (53)
- # boot (56)
- # braveandtrue (1)
- # cider (49)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (57)
- # clojure (403)
- # clojure-austin (17)
- # clojure-dusseldorf (10)
- # clojure-greece (9)
- # clojure-spec (57)
- # clojure-uk (144)
- # clojurescript (60)
- # datomic (149)
- # docker (1)
- # emacs (1)
- # hoplon (23)
- # humor (1)
- # jobs (1)
- # leiningen (2)
- # luminus (1)
- # off-topic (1)
- # om (24)
- # om-next (15)
- # onyx (23)
- # protorepl (2)
- # re-frame (58)
- # reagent (90)
- # remote-jobs (1)
- # ring-swagger (4)
- # slackpocalypse (1)
- # spacemacs (2)
- # specter (18)
- # untangled (4)
- # vim (1)
- # yada (27)
@micha so, we talked a bit a while ago about how to organise elements/components in a hoplon project
@micha how do you organise your on!/do! extensions?
@thedavidmeister i have been defining them in the component namespaces when it's an attribute that launches a component
since the tooltip is absolutely positioned by the tooltip plugin, it doesn't really make sense to have a separate custom element for it
but there are also some do!
attributes that are for working around issues with browser compat or other hacks you need in your specific application for whatever reason
yeah cool
so then do you just require that hacks namespace in the .hl file?
i'm just a bit concerned about not getting clues from the compiler if i use something that doesn't have the right implementation loaded at that point
mostly for the hacks, not the components
that's a cool thing about the new first-class attributes
they can be required/referred/documented just like any other def
vs. maintain a mysterious relationship to elements through the multimethod
@alandipert oh ok, that sounds cool
you'll have to show me how that works sometime 🙂