This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-22
Channels
- # announcements (2)
- # aws (5)
- # babashka (17)
- # beginners (108)
- # calva (28)
- # chlorine-clover (7)
- # clj-kondo (14)
- # cljs-dev (9)
- # cljsrn (2)
- # clojure (118)
- # clojure-europe (50)
- # clojure-finland (5)
- # clojure-france (15)
- # clojure-italy (9)
- # clojure-nl (14)
- # clojure-spec (11)
- # clojure-uk (43)
- # clojuredesign-podcast (1)
- # clojurescript (35)
- # clojutre (2)
- # clr (3)
- # community-development (6)
- # conjure (9)
- # core-async (41)
- # cursive (7)
- # data-science (7)
- # datomic (11)
- # events (1)
- # figwheel-main (4)
- # fulcro (20)
- # ghostwheel (9)
- # graalvm (18)
- # helix (46)
- # leiningen (14)
- # observability (2)
- # off-topic (23)
- # pathom (4)
- # re-frame (5)
- # reitit (5)
- # rum (2)
- # shadow-cljs (32)
- # spacemacs (8)
- # specter (5)
- # sql (36)
- # timbre (3)
- # vim (15)
- # xtdb (2)
- # yada (2)
Should protocols extended via metadata be counted as a usage of a protocol? It currently does not but seems like it should. In the below, IFoo is marked as an unused global declaration.
(defprotocol IFoo
:extend-via-metadata true
(-do-foo []))
(defn new-foo
[]
(with-meta {}
{`-do-foo (fn [])}))
Probably yes, although all the protocol inheritance/usage stuff is half-baked in Cursive ATM. Could you file an issue for that and I'll fix that when I fix the rest?
I'm making an app that has a deps.edn server and shadow-cljs frontend using cursive. cursive seems content on the deps.edn. I'm trying to follow the recommendations for shadow to generate a pom. But i'm not sure how to make cursive aware of the two different project roots. It says to import the project as a pom but i already have it open as a deps.edn project. Is it possible for these two different project styles to live side by side in cursive?