This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-20
Channels
- # adventofcode (17)
- # announcements (1)
- # aws (1)
- # beginners (102)
- # calva (27)
- # cider (16)
- # clj-commons (34)
- # clj-kondo (33)
- # cljs-dev (5)
- # cljsrn (4)
- # clojure (124)
- # clojure-europe (17)
- # clojure-nl (8)
- # clojure-spec (13)
- # clojure-uk (6)
- # clojurescript (68)
- # datahike (21)
- # datomic (23)
- # emacs (3)
- # fulcro (30)
- # introduce-yourself (6)
- # jobs-discuss (6)
- # lsp (31)
- # nextjournal (3)
- # off-topic (1)
- # other-languages (45)
- # portal (4)
- # re-frame (8)
- # releases (4)
- # shadow-cljs (39)
- # specter (6)
- # tools-build (18)
- # tools-deps (11)
I 'published' a blog post on Specter which I would love feedback on. It says March, but actually (for various reasons) it was only published today. It's aimed for beginner/intermediates like me, so the examples might be too obvious for professional developers: http://www.futurile.net/2021/03/20/specter-nested-data-manipulation-for-clojure/
@slgeorge cool, I recommend posting to #news-and-articles
@nathanmarz: Thanks yes I'll post it. Will wait to see if there's any feedback. Hopefully no horrendous mistakes and fingers crossed covered the major use-cases for common usage.
Q: I use Specter everywhere. The one area where I hit limitations has been runtime paths i.e. storing paths in a db and using them at runtime. Basically this isn’t possible without adding a data/dsl on top of each navigator. Has anyone else tried this or seen any clever solutions for this?