Fork me on GitHub
#re-frame
<
2017-05-14
>
sandbags11:05:06

@andre just plugged re-frisk 0.4.5 into a new app and I've noticed that neither handlers nor subs seem to be appearing in the db display. I'm sure they used to. Did something change? Or is my memory faulty?

sandbags11:05:41

@andre i just get :app-db :filter and :app-db-sorted

sandbags11:05:30

ah, it's a setting? Did it use to default to true?

sandbags11:05:42

i have some feeling i have asked you this before

sandbags11:05:01

so thanks &, if so, apologies 🙂

andre11:05:41

i don't remember why i hide it by default, maybe it's better to return it back and show by default

sandbags11:05:15

i think showing it is the better default

sandbags11:05:27

at worst it's a one line distraction

sandbags11:05:26

also app-db and app-db-sorted from the looks of it app-db-sorted is exactly what is sounds, you've sorted the keys, is it valuable to keep both?

sandbags11:05:58

also the filter & views sound like they are introducing something useful but from the readme i cannot work out what the views are doing, and the filter doesn't seem to be introduced. I've poked at the filter but without joy.

sandbags11:05:01

@andre urk... seem to have blown it up, Error rendering component (in re_frisk_shell.core.debugger_shell > re_frisk_shell.frisk.Root > re_frisk_shell.frisk.DataFrisk > re_frisk_shell.frisk.MapNode > re_frisk_shell.frisk.KeyValNode > re_frisk_shell.frisk.DataFrisk)

sandbags11:05:36

ah, okay, i know what happened. I accidentally used assoc instead of assoc-in and ended up with keys that were vectors.

sandbags11:05:46

seems re-frisk barfed on the vectors

sandbags11:05:16

@andre what would be great, and maybe this is what the filter is about, would be to be able to pin certain subs to the top-level

sandbags11:05:26

so you could always see their value