This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-24
Channels
- # babashka (2)
- # beginners (10)
- # calva (30)
- # cljs-dev (3)
- # clojure (40)
- # clojure-europe (8)
- # clojure-france (1)
- # clojure-portugal (1)
- # conjure (4)
- # cursive (12)
- # datalevin (2)
- # introduce-yourself (5)
- # lsp (16)
- # off-topic (33)
- # re-frame (3)
- # rewrite-clj (31)
- # ring (3)
- # shadow-cljs (6)
- # specter (4)
- # tools-deps (8)
- # vim (17)
@onetom I started using my-path=
to distinguish paths from regular function defs.
I think i picked this up from a Hoplon user who would use the “=” to distinguish derived (reactive) “formula” cells/atoms, from regular input (non-reactive) cells/atoms in the Javelin state management system.
Javelin is a lens library, and is useful to encapsulate and name data reading and writing paths. I was also using Specter within Javelin cells. Seemed like a powerful combo to tame any hairy data model for front end use.
thanks, interesting idea! btw, i was also a hoplon user 😉 so how about parametric paths? those would also follow this convention? as we an see on https://github.com/redplanetlabs/specter/wiki/List-of-Navigators the unparameterized navigators are all-caps and the parameterized ones are just regular lower-kebab-case names, without any special convention.