This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-20
Channels
- # announcements (4)
- # babashka (10)
- # beginners (8)
- # calva (13)
- # cherry (20)
- # cider (9)
- # clojure (11)
- # clojure-austin (2)
- # clojure-europe (3)
- # clojure-norway (3)
- # clojurescript (1)
- # datomic (5)
- # dev-tooling (9)
- # fulcro (5)
- # hyperfiddle (5)
- # instaparse (1)
- # lingy (1)
- # malli (21)
- # matrix (1)
- # missionary (9)
- # off-topic (12)
- # releases (2)
- # ring-swagger (8)
- # scittle (9)
- # shadow-cljs (20)
When updating malli dependencies, Cherry got updated from 0c4e0d1de534a4cf910ed7079638dbcfec8ec8b7
to 3f78c7e03e1b940c0cbc05e8c5bc76f8295055cb
, breaking the sci-tests. Seems like the namespace aliases don’t work as expected. Using this config:
(defn -default-sci-options []
{:preset :termination-safe
:aliases {'str 'clojure.string
'm 'malli.core}
:namespaces {'malli.core {'properties properties
'type type
'children children
'entries entries}}})
any ideas what has changed and how to mitigate?@U055NJ5CC alright, I'll wait for the issue
@U055NJ5CC is it about this failing test? https://github.com/metosin/malli/actions/runs/8764828329/job/24055235948 I don't see how this is related to SCI though
forgot, wrote it to cherry: https://github.com/squint-cljs/cherry/issues/130
the failing code uses m/eval
, e.g.
(m/eval "(m/properties [int? {:district 9}])")
doesn’t work anymore with cherry.thanks! m/eval
uses SCI to evaluate the code, to be honest, I have no idea how that works with cherry.
it only uses SCI if you enable SCI. If you enable cherry, m/eval
evaluates through cherry only:
(defn eval
([code] (eval code nil))
([code _opts]
(cond (or (symbol? code)
(seq? code))
(cherry/eval-form code cherry-opts)
(string? code)
(cherry/eval-string code cherry-opts)
:else code)))
(set! malli.core/eval eval)