This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (1)
- # architecture (5)
- # beginners (43)
- # boot (23)
- # cider (5)
- # cljs-dev (143)
- # clojure (42)
- # clojure-austin (4)
- # clojure-dusseldorf (14)
- # clojure-italy (15)
- # clojure-norway (1)
- # clojure-russia (10)
- # clojure-spec (41)
- # clojure-uk (70)
- # clojurescript (262)
- # cursive (3)
- # data-science (18)
- # datomic (66)
- # figwheel (1)
- # fulcro (39)
- # hoplon (21)
- # jobs-rus (1)
- # juxt (4)
- # lein-figwheel (2)
- # leiningen (4)
- # lumo (26)
- # off-topic (4)
- # om (6)
- # onyx (19)
- # parinfer (50)
- # pedestal (9)
- # portkey (10)
- # re-frame (41)
- # schema (5)
- # spacemacs (2)
- # yada (35)
@mikethompson Now that's a community! ❤️ ❤️
hmm. Just tried to upgrade re-frame and it results in clearing my app-db for every request Maybe I’m bumping into that shocker of a breaking change?
I’m adding tracing to see what’s going on. It’s not init. I’ll report back when I know what’s going on
Yeah, sorry. Whenever I do any requests, I modify the
app-db, that in turn seems to blow up existing state entirely
That’s exactly what happens. In prior versions of
re-frame, the first argument to the function passed to
reg-event-db was the existing
db. After the upgrade, it’s just
IIRC (and maybe I don't) I've had a similar incident with the
app-db appearing to be nil in one instance
@hkjels confirming you are using the release from a couple of hours ago?
If so, the tests pass, but the todomvc example doesn't seem to be working along the lines you are talking about. I'm cooking dinner tonight, so will have to look at this in a couple of hours.
But I'd back away slowly from this release for the moment. I must have stuffed something up.
Sorry about that
Hi, I have similar problems in v10, in particular the cofx supplied to
reg-event-fx doesn't have a
:db key, I hope this helps you find the issue
Just posted part 2 of the state machines w/ re-frame post: http://blog.cognitect.com/blog/2017/8/14/restate-your-ui-creating-a-user-interface-with-re-frame-and-state-machines
thanks for this! Your original article was useful during a refactor of my project's main event loop
and now that I'm headed into a pretty major form refactor this will provide some nice inspiration
I’m glad it could help you. I’ve really enjoyed using this approach for a long time. Even though it’s pretty simple and intuitive, it’s great to get feedback that it’s useful to see it written up.
This one is a more detailed walk through of how to do it, still pretty basic. Planning on tackling composing state machines in the next one.
v0.10 of re-frame (just released) is broken. Don't upgrade to it. Wait for v0.10.1 (in about 6 hours).
Sorry for the hassle
@jebberjeb For someone who hates UI development, you sure do blog a lot about it
@jebberjeb starting about a decade ago, game developers started using "behavior trees" instead of FSM. They feel there are significant advantages. In odd moments, I've wondered how they (behavior trees) might play out with re-frame. Warning: this is no more than a thought bubble but given you are interested in the area, I thought I'd mention it.
BTW, I'm not sure you seen it but you might be interested in
re-frame-async-flow. It implements a very specific kind of FSM, in data.