Fork me on GitHub
#re-frame
<
2016-03-15
>
amacdougall00:03:56

Fun re-com question... I noticed that Chrome's autofill pre-populates my re-com/input-text fields. This is a good thing! However, with the default change-on-blur behavior, that means that the input field changes won't be picked up at all if the user just hits Submit on the autofilled form. I'm going to just set :change-on-blur? false for most fields and call it a day, but I'm curious if anyone has a suggestion for picking up the autofill data once and switching to change-on-blur for user input. Everything I can think of involves storing a form-specific flag in the app db (or in a form atom or whatever).

hugobessaa09:03:22

@mikethompson: have we found our three letter acronym? Maybe DDE. Derived Data Everywhere. Then, let's make that T-Shirt!

hugobessaa09:03:51

@mikethompson: reading the readme again, you wrote that too :P

hugobessaa09:03:15

> re-frame tries to be Derived Data everywhere, flowing. Or perhaps, Derived Data All The Way Down (an infinite loop of Derived Data).

mikethompson09:03:06

Ah, no wonder I liked it.

mikethompson09:03:46

I seem remember at the time being delighted to discover how we could use enrich middleware to handle error/warning checking.

hugobessaa09:03:59

I'm now enjoying these beautiful dynamic subscriptions and a normalized app-db.

mikethompson09:03:57

Yeah nice. I'm acutely aware of the power that full FRP solutions have (full Signal graphs). But I'm also cautious, bordering on suspicious, of any approach which promotes the distribution of state (across a Signal graph). I kind a love all my data in the one place. I give up a little power, but buy masses of simplicity.

mikethompson09:03:19

I mention this only because, when you think about it, dynamic subscriptions are a fancy little way of creating a point in the Signal graph.

mikethompson09:03:19

@hugobessaa: BTW, I'm flattered that anyone remembers my jokes. Thanks!

hugobessaa10:03:00

I'm really interested too. I'm using it just like you described.

hugobessaa10:03:21

backend people read the re-frame readme and laughed over some of the jokes at our slack channel

nonrecursive13:03:07

@mikethompson: I am a big fan of your jokes and that README

cky16:03:09

@mikethompson: FWIW the one-source-of-truth style is also the approach taken by Redux. Now, Redux doesn’t operate the same way as re-frame (and I happen to like the re-frame approach), but the one-data-store idea is definitely a widely supported approach. 👍