This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-06
Channels
- # announcements (58)
- # babashka (43)
- # babashka-sci-dev (22)
- # beginners (8)
- # biff (8)
- # calva (62)
- # circleci (3)
- # clerk (6)
- # clj-kondo (27)
- # cljsrn (9)
- # clojure (61)
- # clojure-austin (4)
- # clojure-conj (3)
- # clojure-europe (11)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-norway (4)
- # clojure-spain (5)
- # clojure-uk (2)
- # clojurescript (51)
- # data-science (1)
- # datascript (4)
- # emacs (33)
- # events (14)
- # funcool (14)
- # gratitude (13)
- # introduce-yourself (1)
- # jobs (9)
- # lsp (58)
- # malli (23)
- # missionary (31)
- # nextjournal (9)
- # off-topic (35)
- # proletarian (2)
- # re-frame (5)
- # remote-jobs (7)
- # shadow-cljs (2)
- # spacemacs (7)
- # sql (26)
- # testing (12)
- # vim (1)
- # web-security (3)
- # xtdb (2)
Say if I want to model rounds in a game. Is there an elegant way of doing that? Currently, I just have entity-name/round 1 etc for an entity that happened during round 1 and tracking :round/current as an update in place value. But that seems awkward. I feel like ideally round should be a reference to a round entity rather than just a value. Something like entity-name/round [round/number 1]. Is there a convention/standard approach for modeling desecrate time like rounds/turns in datascript? thanks.
Same with other databases, I think this is called normalization? You want round to be its own entity and reference it by :round/id
Thanks for the quick reply! So it is that straight forward. Just wanted to make sure there wasn’t some fancy datascript/datomic thing I was missing. 😅
Absolutely loving this library. It’s really nice for doing game state. Thank you for making it!