This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-09
Channels
- # announcements (12)
- # beginners (159)
- # boot (3)
- # calva (41)
- # cider (48)
- # clara (2)
- # clj-kondo (8)
- # cljdoc (8)
- # clojure (70)
- # clojure-dev (10)
- # clojure-europe (2)
- # clojure-losangeles (1)
- # clojure-nl (12)
- # clojure-spec (7)
- # clojure-uk (63)
- # clojurescript (24)
- # cursive (24)
- # datomic (22)
- # expound (17)
- # figwheel (1)
- # fulcro (176)
- # graphql (23)
- # jobs (9)
- # jobs-discuss (56)
- # kaocha (1)
- # mount (3)
- # nyc (1)
- # off-topic (91)
- # onyx (3)
- # overtone (4)
- # pathom (3)
- # pedestal (1)
- # re-frame (11)
- # reitit (19)
- # ring (8)
- # shadow-cljs (16)
- # test-check (5)
- # testing (2)
- # tools-deps (20)
- # vim (9)
It would be cool if figwheel could throw a notification on browser caching... Basically, watch what its streaming down to the browser, diff the dom, if the dom isnt inline with what was streamed down, throw a "Potential Cache 'Code-Hiding' Warning" Just wasted a day assuming it was my bad/noob clojure coding skills when it turned out to be browser caching... Which... brings me to a whole other question (totally unfig related).... when/where/why does the browser suddenly decide to cache and keep the cache. I am working on a simple feature -- the same across multiple components in our system. In the first few instances of applying it, it worked no problem but, in this one, the browser decided to cache a previous peice of code I wrote and hang on to it... leading me to believe I had a bug in my code that I didnt understand. However, the final implementation code is the same for each instance Ive applied it to -- save for an on-click handler -- ive taken the same process each time to developing it and, in all instances but this one, it was never cached but, this time it was.