Clojurians Log v2
Clojure programming
Channels
Apps
matrix
Weathercold 2024-04-02T22:26:20.288269Z
I was reading the flutter-mx source code when I saw keywords being used instead of vars. I'm pretty sure this is a bug and will always evaluate to true. https://github.com/kennytilton/flutter-mx/blob/8db71c06f7ce2cb6a5f48f7645d037e2d122ecc1/src/tilton/mx/model/navigate.cljd#L147 There are several other occurrences below at L153, L160, L165, L172 and L175
🙀 1
kennytilton 2024-04-02T22:44:16.009259Z
Thx, I will fix those. Must have been a global edit gone bad. That never popped up because I never navigate with the possibility that my goal does not exist, so I always specify :must? true. Indeed, you have me wondering if I should lose the option! But it cannot hurt.
kennytilton 2024-04-02T22:52:52.300069Z
I guess the thing is this: MX UIs have conditional structure, and those conditions read reactive state S', but whether conditional structure exists -- which would indeed work reactively as S'' -- is not how the app makes decisions, it goes off the source state S'. This is important because S'' is incidental to S', altho determined by it. And it is always better to go with the source, because how S'' gets decided could vary in the face of the same S'. For example, instead of not building an element because of S', we might just make it invisible. Never really thought about it, except to notice I never branch off UI structure existence.