This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-17
Channels
- # beginners (10)
- # boot (9)
- # cider (1)
- # cljs-dev (191)
- # clojure (77)
- # clojure-russia (4)
- # clojure-serbia (10)
- # clojure-spec (19)
- # clojure-uk (4)
- # clojurescript (16)
- # core-async (9)
- # cursive (1)
- # data-science (1)
- # datomic (3)
- # emacs (42)
- # graphql (2)
- # hoplon (38)
- # jobs (1)
- # jobs-discuss (18)
- # luminus (3)
- # lumo (20)
- # off-topic (9)
- # om (51)
- # parinfer (3)
- # pedestal (8)
- # re-frame (4)
- # reagent (7)
- # rum (9)
- # sql (9)
- # untangled (81)
I just pushed 7.1.0-SNAPSHOT
this version includes optional :pre/:post
conditions and optional docstring support for elements.
@alandipert do you have a small project you could test?
@flyboarder how much of a jump is it between 7.0.1
and 7.1.0
?
@thedavidmeister just the defelem
docstring and pre/post conditions
also 7.0.2
includes the goog
attribute fix
also, i haven't tried this, but does defelem
support meta data?
no, which is why I opted to specifically include the docstring metadata
ok, so it would support meta data in 7.1.0?
this is a 7.0.1
elem (defelem my-elem [attr kids] (div attr kids))
this is a 7.1.0
elem (defelem my-elem "My Custom Element" [attr kids] {:pre [] :post []} (div attr kids))
where the docstring and pre/post map are optional
oh yeah, but can i put my own metadata on a 7.1.0 defelem?
although post conditions will always get the element constructor since thats what defelem returns
no custom metadata
ah ok, maybe in the future 🙂
ie. (defelem ^:something val my-elem [attr] kids...
doesnt work
@meeli and i were just talking about the idea of putting metadata on defelem that can autogenerate a devcards-ish styleguide
the more of that you want the more we need to reimplement defn
or reimplement it’s argument parsing
im working on a hoplon.spec
lib right now
something to show soon….
so the idea is that we'll swap out the current tests with that?
and then have something to build future tests for core on top of?
yep, ideally we can solve half the issue with specs for hoplon macro’s and the other half by having attribute providers write tests for their attributes, custom elements would use the :pre conditions for local attributes
ok cool
well, i'm into that 🙂
Hello, I'm a Hoplon (and Clojure) beginner and am trying to get Hoplon working with Korma. I try to require Korma in an index.cljs.hl like this: (page "index.html"
(:require korma.core korma.db)) ... but I keep getting: No such namespace: korma.core
When I do boot show -d
Korma is listed, I have appended it to the :dependencies list in my build.boot:
[korma "0.4.3"]
├── [com.mchange/c3p0 "0.9.5.2"]
│ └── [com.mchange/mchange-commons-java "0.2.11"]
└── [org.clojure/java.jdbc "0.6.1"]
[mysql/mysql-connector-java "5.1.6"]
i think that for .hl
files you need to wrap dependencies in a vector
@mdo generally no, you would access it from your backend, usually clojure
or you would implement something like pouchdb