This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-08
Channels
- # announcements (12)
- # aws (4)
- # beginners (92)
- # calva (2)
- # cider (28)
- # clara (11)
- # clj-kondo (5)
- # cljdoc (9)
- # cljs-dev (195)
- # cljsjs (1)
- # clojure (82)
- # clojure-italy (18)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (51)
- # clojurescript (40)
- # cursive (7)
- # datomic (19)
- # duct (9)
- # emacs (2)
- # figwheel (3)
- # fulcro (56)
- # graphql (8)
- # jobs (3)
- # luminus (2)
- # off-topic (15)
- # re-frame (5)
- # reitit (3)
- # ring (5)
- # shadow-cljs (22)
- # slack-help (2)
- # sql (51)
- # test-check (9)
- # vim (64)
- # yada (1)
Another alternative is to override user deps.edn
with another one that contains the required dependency. According to settings, it's a per-project parameter. But it still may be considered ever more ickier than the alias way.
Does Cursive have support for test.check
? Out of the box it has wrong indentation on prop/for-all
, does not understand that it creates bindings (and thus complains about "... cannot be resolved"), bad indentation for defspec
& doesn't understand it defines a new thing, thus complaining about its name "... cannot be resolved"). I googled out https://cursive-ide.com/userguide/testing.html but it does not mention test.check. Thank you!
I know that it doesn't really answer the question, but you can Alt+Enter on any symbol in question and play around with "Configure indentation for [...]" and "Resolve [...] as..." I find that most of the time, it helps with such cases.
Thanks, will try!
Yes, you should be able to fix those problems using the customisation, but test.check is popular enough that I should fix that.