This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-21
Channels
- # bangalore-clj (1)
- # beginners (60)
- # boot (30)
- # cider (7)
- # cljs-dev (10)
- # cljsrn (2)
- # clojure (163)
- # clojure-conj (10)
- # clojure-france (1)
- # clojure-greece (2)
- # clojure-italy (7)
- # clojure-russia (41)
- # clojure-serbia (22)
- # clojure-spec (41)
- # clojure-uk (41)
- # clojurescript (178)
- # cursive (36)
- # datascript (1)
- # datomic (23)
- # dirac (38)
- # graphql (12)
- # hoplon (20)
- # immutant (32)
- # instaparse (3)
- # keechma (1)
- # lein-figwheel (18)
- # leiningen (8)
- # liberator (1)
- # luminus (30)
- # lumo (29)
- # off-topic (18)
- # om (17)
- # pedestal (7)
- # planck (37)
- # precept (1)
- # re-frame (67)
- # ring-swagger (2)
- # timbre (1)
- # untangled (8)
- # vim (2)
@flyboarder oh i see
so is the idea that :on
and :do
are now much stricter about what data they will accept?
e.g. :toggle
could only accept a boolean?
@thedavidmeister exactly, however the runtime specs are heavy so you turn them on for development and off for production, you can always use the new pre/post map support to check the arguments if you want them to run always
@flyboarder really impressive work you're doing there!
@flyboarder that's pretty cool, i just wonder how many errors i will see as soon as i turn it on 😕
also, the addition of spec.alpha
means i will be forced to upgrade to the new ns
so, there's going to be some hoop jumping to upgrade to this one
@flyboarder also, how hard is it to turn them off in development?
@flyboarder sorry i did not understand
@flyboarder what you said about .target.files
hey @avabinary 👋
@alandipert thanks!
@thedavidmeister really easy to turn it on just call hoplon.core/spec!
on your index page, by default it's off. Clojure 1.9 will probably be released with alpha spec anyway but we will see. There are only about 100 issues remaining for 1.9 and most of them are for spec.
@jouerose the event object you are receiving from the change event contains an original event object, which has a property called target, which has another property called files. This files property is the list you are looking for.
This is driving me insane, might be a timbre thing instead of hoplon, but anyone know why timbre/error is working and logging to js console, but timbre/debug isn't showing anything? This is from a fresh hoplon template directory:
(page "index.html"
(:require
[taoensso.timbre :as timbre
:refer-macros [log trace debug info warn error fatal report
logf tracef debugf infof warnf errorf fatalf reportf
spy get-env]]))
;;(enable-console-print!)
(timbre/set-level! :trace)
(debug "hello world")
(error "error")
(html
(head
(link :href "app.css" :rel "stylesheet" :type "text/css"))
(body
(h1 "Hello, Hoplon!")))
@jjttjj where are the logging levels documented? do you need the :debug
level?
Can't seem to find the documentation for levels, but I recall trace being lower than debug, and it doesn't work if i set the level to :debug either. This is probably more a Timbre issue than hoplon at this point though
I would say so, I also can’t find the documentation for levels. But if debug doesn’t work either it’s probably timbre.