This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (63)
- # cljs-dev (1)
- # cljsjs (1)
- # cljsrn (11)
- # clojure (208)
- # clojure-berlin (2)
- # clojure-dusseldorf (5)
- # clojure-italy (5)
- # clojure-norway (56)
- # clojure-russia (7)
- # clojure-spec (85)
- # clojure-uk (27)
- # clojurescript (191)
- # core-async (73)
- # cursive (4)
- # datomic (62)
- # defnpodcast (1)
- # hoplon (2)
- # jobs-rus (1)
- # juxt (14)
- # keechma (1)
- # leiningen (1)
- # lumo (126)
- # off-topic (2)
- # om (11)
- # onyx (27)
- # pedestal (52)
- # planck (21)
- # powderkeg (1)
- # re-frame (32)
- # reagent (14)
- # ring-swagger (1)
- # rum (3)
- # slack-help (19)
- # specter (23)
- # untangled (32)
- # vim (7)
- # yada (43)
@stephenway Are you using PostCss for everything or combining it with
om-css from untangled repo ? Really like the idea of co-located css.
Is there a easy/recommended way in untangled to do something like.
Fire up the data fetch only after 1sec has passed since the last filter was applied.
@claudiu Right now it’s only using PostCSS to compile, and we have looked at using om-css, but currently do not have the bandwidth to convert it to such a state. I think it would be awesome to have colocated styles though!
@stephenway is anybody using om-css in production or is it still experimental ?
@claudiu Not that I am aware of. Maybe the guys at adstage? No reason not to use it in production that we can see.
We are using: https://github.com/ladderlife/om-css in production
That is the other om-css
@mitchelkuijpers thank you, missed that one. Will check it out 🙂
But we are looking into wrapping https://styled-components.com/
Maybe something that you can use garden instead of the strings
But we are waiting for the js-modules to get a little bit more mature
@claudiu Mutations are meant to be abstract...so the filters should be calling some
set-filter kind of mutation, and the debouncing should be done in the mutation implementation (for fetch). In terms of implementing that: For example: you could have an atom that is "private" to that set of filter mutations that holds onto a js timer that you reset at each mutation...if it expires, it could then run a
load against the reconciler or component (which you can get from the component passed to the mutation in env).
I'd typically recommend the reconciler or the
(app-root reconciler) be the thing used with load (in that kind of scenario), since the component that triggered the mutation could get un-mounted due to user navigation in the UI before the timeout.
The ladderlife om-css requires you use a custom
defui (which leads to better ability to export the CSS for post-processing and use as a file). The untangled version approach is less invasive, but expects that you'll have the CSS embed into the DOM without using a file.
My thought was that having cljs to manipulate the CSS was sufficient, but there are some powerful pre-written CSS tools out there. pros/cons 😄
@tony.kay ok 🙂 I could not find anything regarding om.next middleware. I had a lot of fun with https://redux-observable.js.org/ and was curious if I could use a similar in om.next/untangled.
the problem is you need to understand the model before you start trying to mix and match tech
when you ask a direct question like debouncing filter updates, that I answer clearly...when you ask about integrating redux...I'm no expert on that topic, nor do I plan to research it for you 😉
agh 😄 not really about integrating redux. Switching from js/redux to clojure & untangled. Was just curious if there was a similar pattern.
think you'll find that Untangled/Om Next has a similar simple nature to Redux...from what I know aabout it at least
yes, thank you so much for the video series 🙂 a few of them I have watched more than once.