This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-25
Channels
- # aleph (15)
- # beginners (65)
- # boot (46)
- # chestnut (3)
- # cider (1)
- # clara (11)
- # cljs-dev (5)
- # cljsjs (4)
- # cljsrn (13)
- # clojure (180)
- # clojure-dev (2)
- # clojure-italy (10)
- # clojure-russia (62)
- # clojure-spec (6)
- # clojure-uk (85)
- # clojurescript (45)
- # community-development (11)
- # crypto (3)
- # cursive (10)
- # datomic (94)
- # defnpodcast (2)
- # fulcro (4)
- # heroku (1)
- # hoplon (4)
- # jobs (3)
- # juxt (10)
- # leiningen (1)
- # luminus (4)
- # mount (13)
- # music (1)
- # off-topic (10)
- # onyx (2)
- # portkey (15)
- # proton (2)
- # re-frame (16)
- # reagent (10)
- # shadow-cljs (194)
- # spacemacs (2)
- # specter (2)
I'm looking for a way to avoid my ajax auto-complete glitching.
As I type, new ajax requests fetch data.
That means there's a period where no results are available.
I found this in the docs. https://github.com/Day8/re-frame/wiki/Subscribing-To-A-Database#some-code
Seems a bit clunky.
The behaviour I'd like is "keep showing the old list while I'm fetching new results"
I'm doing a deal with the devil for now. Should be fine in my use case...
(r/create-class
{:should-component-update
(fn [_ _ [_ props]]
(not (:loading props)))
I don't see the reason why would you need to display empty results set
there must me something cleaning the cache while next req is in-flight
I use a sub for fetching results. The sub returns immediately with a loading state, then updates when values are available.
so you're replacing prev. results with loading state when req is issued?
why not have them side-by-side?
Is there something akin to re-frame but for server side programs? I have a huge service that handles websockets, message queues and relatively big global, dynamic state. I can see some benefits in re-writing it using re-frame concepts.
@nooga a CQRS architecture is one way of interpreting re-frame on the server