This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-24
Channels
- # beginners (15)
- # boot (4)
- # cider (1)
- # cljs-dev (2)
- # cljsrn (5)
- # clojure (124)
- # clojure-france (2)
- # clojure-russia (22)
- # clojure-uk (10)
- # clojurescript (50)
- # core-async (5)
- # cursive (3)
- # datomic (8)
- # emacs (2)
- # fulcro (10)
- # hoplon (8)
- # jobs (4)
- # luminus (2)
- # lumo (7)
- # off-topic (14)
- # portkey (7)
- # re-frame (22)
- # reagent (2)
- # shadow-cljs (3)
- # spacemacs (1)
- # yada (26)
@favila , missed your comment in response to my question about schema naming conventions. I think my :tag
was meant to be equivalent to your :tag/name
. Is the idea that yours is more explicit? The domain tag indicates what the entity is; whereas 'name' is the property of the domain. So : domain/property
is the convention? I have also seen the use of a .
in some cases. Do you ever use that? Is there some canonical basis to the conventions being used here?
It mirrors the conventions datomic itself uses e.g. :db/cardinality :db.cardinality/one) and is a natural fit with clojure keyword and symbol namespace naming @ezmiller77
I was confused in your example that you said a tag was an entity but the attribute was a keyword type
> you said a tag was an entity but the attribute was a keyword type good point!
That makes sense that the conventions mirror datomic itself. In this example -- :db.cardinality/one
-- what is the .
saying?
@ezmiller77 think java package names
@favila: I'll look it up. I haven't used Java since college. :0)