This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-24
Channels
- # announcements (2)
- # beginners (130)
- # calva (72)
- # cider (4)
- # cljdoc (15)
- # cljs-dev (3)
- # cljsrn (2)
- # clojars (4)
- # clojure (55)
- # clojure-nl (1)
- # clojure-uk (19)
- # clojurescript (46)
- # cursive (95)
- # datomic (6)
- # figwheel (40)
- # fulcro (12)
- # hyperfiddle (3)
- # off-topic (11)
- # onyx (3)
- # parinfer (6)
- # pathom (15)
- # protorepl (38)
- # re-frame (67)
- # reitit (18)
- # shadow-cljs (45)
- # tools-deps (2)
Fulcro 2.6.16 on Clojars. Has a simple bug fix for mutation remote detection that was affecting @levitanong when using UI state machines with custom remotes.
Snapshot feature seems problematic in inspect. When restoring snapshots it still renders with old props unless the ident changes
Props changes as expected, but renders with old value
"Force app re-render" doesn't help
there are a lot of things that can go “wrong” with snapshots, but the feature itself is trivial (copy the state back to your app and force a root render). Your code changes can make a snapshot irrelevant, and chaning a UI query requires a UI reload…so the problem you’re seeing is probably not inspect/snapshots itself @andreas862
This was using snapshots without making any changes to the code between snapshotting and reverting
Only doing mutations to state
which also can be seen in the inspector when restoring snapshots
Tried activating "Paint flashing". Nothing happens when I push "Force app re-render". Even though a prop value has been changed
unmanaged inputs - does of course not play nice with the re-render
Sorry, thanks for the help
oh...you're saying your problem was unmanaged inputs? Yeah, that matters. There is one other thing that can go wrong: inspect is in a chrome extension, and for security it cannot see the actual app state...the database changes are "sync'd" to it via serialization. If you put things in app state that don't serialize, then that'll not work either.