This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-15
Channels
- # announcements (8)
- # beginners (65)
- # calva (25)
- # cider (11)
- # clj-kondo (9)
- # cljsrn (14)
- # clojure (103)
- # clojure-europe (15)
- # clojure-greece (1)
- # clojure-italy (28)
- # clojure-nl (39)
- # clojure-spec (9)
- # clojure-uk (28)
- # clojuredesign-podcast (37)
- # clojurescript (56)
- # cursive (41)
- # data-science (10)
- # datomic (25)
- # duct (1)
- # emacs (1)
- # events (3)
- # figwheel-main (7)
- # fulcro (9)
- # graalvm (7)
- # graphql (10)
- # jobs (2)
- # nrepl (17)
- # off-topic (40)
- # quil (12)
- # reitit (11)
- # remote-jobs (5)
- # rum (2)
- # shadow-cljs (387)
- # sql (22)
- # tools-deps (8)
- # vim (26)
- # xtdb (47)
- # yada (9)
Hello, I came across a curious behavior in Cursive today. Even though the functions like f.a.denormalize/add-union!
are defined as private - Cursive still suggests them for code-completion.
As far as I understand, the private defs shouldn’t be coming up there - or am I missing something here?
I’m on fulcro-3.0.4
and here’s the def for reference https://github.com/fulcrologic/fulcro/blob/a0cf2957250ed6fa3819d00a5acbc2f0b66b7eaa/src/main/com/fulcrologic/fulcro/algorithms/denormalize.cljc#L121
its fine to complete on private methods, you can actually call them using a trick: (#'some-ns/private-fn "bla")
I see private is more a hint of "this may not be supported on future" than a hard "you can't call this"
There's a #cursive channel as well. Although I think Colin (cursive programmer) is pretty busy at the moment.
Ah, I see - thanks @U066U8JQJ and @U0D5RN0S1 ( yeah, the cursive channel is jam packed already and I just had a minor doubt 🙂 )
@U066U8JQJ, but I think that then there’s no way to distinguish from outside whether a function if private or not?
Nice one @U2J4FRT2T!