This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-23
Channels
- # announcements (19)
- # babashka (6)
- # beginners (47)
- # cljs-dev (4)
- # cljsrn (3)
- # clojure (18)
- # clojure-australia (3)
- # clojurescript (50)
- # code-reviews (1)
- # conjure (16)
- # datomic (6)
- # editors (4)
- # emacs (1)
- # fulcro (10)
- # graphql (3)
- # helix (7)
- # jackdaw (10)
- # malli (1)
- # off-topic (3)
- # pathom (4)
- # sci (2)
- # shadow-cljs (39)
- # testing (3)
- # tools-deps (5)
- # vscode (1)
Question about optional query inputs: https://ask.datomic.com/index.php/616/how-to-gracefully-handle-optional-query-inputs
On mobile so can’t write a full form answer but for these use cases, we’ll build queries programmatically. i.e., cond-> :in and :where.
➕ 3
I got a prototype of this working just before reading this. It’s actually a bit easier than I first anticipated.
@U083D6HK9 do you happen to use this technique to inject authorization constraints onto queries as well? Authorization seems to touch every query in my system, and it occurred to me I might be able to append those rules onto queries using generic helper functions..