This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-04
Channels
- # announcements (2)
- # beginners (30)
- # calva (30)
- # cider (10)
- # cljs-dev (4)
- # clojure (59)
- # clojure-nl (2)
- # clojurescript (21)
- # cursive (22)
- # datascript (3)
- # datomic (5)
- # duct (5)
- # figwheel-main (1)
- # flambo (2)
- # fulcro (8)
- # jackdaw (1)
- # joker (9)
- # off-topic (24)
- # pathom (1)
- # re-frame (2)
- # rewrite-clj (4)
- # shadow-cljs (163)
- # sql (14)
- # tools-deps (6)
- # vim (24)
- # yada (3)
@dfornika thanks for taking a look. It really is a joy to model at the attribute level. Both Val’s and Tiago’s ideas inspired my own with this, and I’ve been exploring ways to take it further. For example, I think it would be interesting to add attributes to the “meta schema” like :private? (true|false)
to allow for mechanical results (as Hodur calls them) surrounding access control. It could obviously be more complex than a boolean value, but I can imagine, for example, a simple datom syncing service that strips private content before sending it to listeners.
Or maybe :persisted?
, which can be used to strip transient attributes from domain maps before being stored in a database...
Working at the attribute level opens up many interesting possibilities (and surely its own complexities too).
Hey @U6GFE9HS7... happy something I explore and love sharing has inspired you! See you in November.