This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-26
Channels
- # beginners (20)
- # cider (59)
- # cljsrn (6)
- # clojars (7)
- # clojure (91)
- # clojure-boston (1)
- # clojure-dusseldorf (3)
- # clojure-finland (1)
- # clojure-italy (8)
- # clojure-losangeles (1)
- # clojure-nl (16)
- # clojure-spec (25)
- # clojure-uk (113)
- # clojurescript (126)
- # core-async (27)
- # cursive (5)
- # data-science (3)
- # datomic (22)
- # emacs (24)
- # fulcro (30)
- # garden (7)
- # graphql (7)
- # leiningen (3)
- # nginx (1)
- # off-topic (63)
- # onyx (13)
- # portkey (1)
- # re-frame (1)
- # reagent (28)
- # shadow-cljs (92)
- # tools-deps (1)
- # uncomplicate (1)
- # vim (24)
- # yada (8)
Is it possible/advisable to have a trigger based on window state?
You mean decide whether to trigger based on what is in the window state?
If so, yes, that’s perfectly fine. You can set :window-state
in http://www.onyxplatform.org/docs/cheat-sheet/latest/#trigger-entry/:trigger/state-context. That way Onyx will not maintain trigger state.
I take it in that case you only need :trigger/trigger-fire?
in the trigger definition.
IIRC, yes.
Does onyx-local rt support water mark functionality? e.g
:onyx/assign-watermark-fn ::watermark-fn
:trigger/on :onyx.triggers/watermark
:trigger/state-context [:window-state]
@drewverlee should do, though it’s possible we don’t support window-state triggers yet. I think we do though.
@dbernal yes. You will end up with hash-routing on the group-by key, and if you have say 10 peers, you will always end up with the same group key on the same peer slot.
onyx-plugin template 0.12.7.1 is out https://github.com/onyx-platform/onyx-plugin, thanks to the hard work of Joaquim Torres on our gitter.
It’s a really big deal as it had not been updated for the new plugin model yet.