This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-16
Channels
- # aatree (1)
- # admin-announcements (6)
- # alda (3)
- # beginners (66)
- # boot (41)
- # cider (4)
- # cljsjs (3)
- # cljsrn (18)
- # clojure (146)
- # clojure-android (2)
- # clojure-nl (1)
- # clojure-russia (35)
- # clojure-sdn (2)
- # clojure-sg (5)
- # clojure-uk (41)
- # clojurescript (116)
- # datomic (12)
- # dirac (40)
- # docker (2)
- # editors (2)
- # hoplon (85)
- # immutant (19)
- # jobs (1)
- # keechma (2)
- # lein-figwheel (8)
- # mount (33)
- # off-topic (1)
- # om (114)
- # onyx (159)
- # parinfer (24)
- # proton (3)
- # reagent (4)
- # ring-swagger (15)
- # uncomplicate (7)
- # untangled (93)
- # yada (30)
would alembic work? I think I’ve only tried it with Clojure backend projects and it does wonders there. https://github.com/pallet/alembic
Is there a way I can tell if a reagent component update (or re-mount) is caused by a figwheel reload?
@pez put a logging statement in your reload?
@danielcompton: I was unclear. I mean if there's a way for my component to know.
not AFAIK, although if you need to make that distinction it suggests something might not be quite right in the reloading code
But I don’t know the context, so I might be wrong.
I'm not ruling that out. The context is that my app relies on HTML5 pushstate (via Accountant) and I seem to need to handle scrolling to the top of each new page myself. I've got it somewhat working, but it has the side effect of my pages scrolling to the top when I make changes to the page in development. I was thinking I could close that side effect if only I could tell if it was a code reload triggering the update of my page component.