This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-02
Channels
- # announcements (2)
- # beginners (69)
- # boot (1)
- # cider (35)
- # clara (1)
- # cljs-dev (1)
- # clojure (40)
- # clojure-spec (11)
- # clojure-uk (8)
- # clojurescript (9)
- # cursive (1)
- # datomic (5)
- # figwheel-main (25)
- # fulcro (64)
- # jobs (2)
- # jukebox (1)
- # kaocha (3)
- # off-topic (7)
- # pathom (39)
- # planck (5)
- # random (1)
- # re-frame (11)
- # reagent (8)
- # shadow-cljs (58)
- # test-check (41)
- # vim (13)
otherwise yes, it wouldn't be hard to just put a thing in your app-db to trigger a render of the notification
The auto-dismiss portion can be a setTimeout
that does something along the lines of (rf/dispatch [:clear-notification ...])
.
i’m trying to not have to call addNotification
after some subscription though - i’m looking at material ui snackbar now. have you used one that you like?
I'm confused about how you'd want to get the notification to pop up... usually the notification is basically a side-effect of some event (or something that has happened)
right - i’d dispatch :add-notification
, which would append some map to my :notifications
list in the app db (so i have 3 notification maps in the list in the db) - i’d like to have some view that says for notification in notifications: [my-notification notification-props]
(pseudocode…)
Yep -- that's basically how I've done it. We rolled our own with relatively little code