This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-15
Channels
- # architecture (5)
- # babashka (34)
- # beginners (72)
- # calva (42)
- # cherry (31)
- # cider (14)
- # clojure (27)
- # clojure-europe (11)
- # clojure-norway (17)
- # clojure-uk (1)
- # clojurescript (25)
- # community-development (13)
- # conjure (1)
- # core-async (11)
- # datascript (18)
- # datomic (11)
- # emacs (12)
- # fulcro (10)
- # integrant (5)
- # introduce-yourself (3)
- # jobs (8)
- # juxt (2)
- # malli (22)
- # off-topic (11)
- # pathom (18)
- # polylith (62)
- # rdf (18)
- # reagent (8)
- # releases (1)
- # shadow-cljs (35)
- # sql (3)
- # squint (141)
- # tools-deps (12)
- # vim (4)
- # xtdb (4)
If i always refer to a java class with its fully qualified name, do i still need to add it to ns :import declarations ?
IIRC :import had some extra nuance relative to static class initializers, I can be wrong though
no, import does not load the class
it just updates the namespace mappings
is there a way of type hinting proxy-super? On this code and `*warn-on-reflection*`:
(proxy [javafx.scene.control.ListCell] []
(updateItem [item empty?]
(proxy-super updateItem item empty?)
))
I'm getting call to method updateItem can't be resolved (target class is unknown).
Here's an example of how nREPL does it: https://github.com/nrepl/nrepl/blob/d875260afcecd6bfc2ff53a0be437cf2972250f4/src/clojure/nrepl/middleware/session.clj#L135
damn, thanks!
found this https://clojure.atlassian.net/browse/CLJ-1433 also
hmm but doesn't work on my case :thinking_face:
Don't know for sure but maybe this is why: https://github.com/cljfx/cljfx/blob/master/src/cljfx/fx/table_cell.clj#L27
oh yeah, that may be it
@U2FRKM4TW out of curiosity, what was your approach for finding that comment?
Full text search for proxy-super
in one of my projects that has a lot of dependencies. :)
haha nice
@U0739PUFQ http://grep.app can also be super helpful in https://grep.app/search?q=proxy-super&filter[lang][0]=Clojure
Is there a way to add a custom error message to spec if a s/def fails?
I'm not sure about doing this through spec directly, but i think expound allows for this. https://github.com/bhb/expound Expound is what i use for custom human readable errors for spec.
malli can probably do this to as it's more a batteries included.
No, not really. You can provide a custom explain function overall by binding clojure.spec.alpha/explain-out but you're kind of taking over the whole explain printing job then