This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-23
Channels
- # announcements (12)
- # beginners (225)
- # calva (7)
- # cider (45)
- # clj-kondo (1)
- # cljdoc (1)
- # cljsrn (3)
- # clojure (112)
- # clojure-dev (45)
- # clojure-europe (6)
- # clojure-finland (2)
- # clojure-india (1)
- # clojure-nl (27)
- # clojure-spec (37)
- # clojure-uk (171)
- # clojurescript (39)
- # core-async (9)
- # cursive (22)
- # datascript (8)
- # datomic (50)
- # emacs (12)
- # figwheel-main (17)
- # fulcro (42)
- # garden (2)
- # hoplon (27)
- # jobs (4)
- # kaocha (8)
- # klipse (2)
- # luminus (2)
- # off-topic (9)
- # perun (33)
- # planck (2)
- # re-frame (9)
- # reagent (48)
- # reitit (5)
- # remote-jobs (1)
- # rum (2)
- # shadow-cljs (23)
- # slack-help (3)
- # spacemacs (18)
- # sql (7)
- # tools-deps (24)
- # unrepl (9)
- # vim (30)
@tony.kay @wilkerlucio @conan Ok, I think I’ve fixed #1908. Basically, keywords will act as they did before the keyword definition change, but you can still navigate to the definition sites (if there are any) and they will still show up in structure view.
Thanks for letting me know, that's fantastic! I'm now in an all-emacs team so I value this stuff beyond the functional =D
One thing though - currently if there’s a destructuring like:
(defn f [{::b/keys [x y]}]
and I rename ::b/y
to :other/baz
, the destructuring will be changed to:
(defn f [{:keys [::b/x :other/foo]}]
Basically right now a :keys
destructuring will never be split, just the prefixes will be adjusted to ensure the code is correct.
@cfleming I had no idea what Tools→REPL→Clear all test markers meant until I read the docs. Wouldn't "Clear all test errors" be clearer?
And, regarding Re-run last test action in REPL, what is a "test action"? When I run (test-var #'my-test)
in the REPL, does that constitute a test action? If not 1) what are test actions, 2) is there a way to run a single test via keystrokes? Thank you!!!
2) yes, what you're looking for are: REPL > Run tests in current NS in REPL REPL > Run test under caret in REPL they'll let you run all or one test in a ns via a keystroke
1) I'm not sure exactly what constitutes a test, for my use cases it's always the entire contents of one deftest
, including fixtures
incidentally, if you have some code you want to re-run over and over from a keystroke, you can add REPL commands and bind them to keystrokes; for example, i always have (go)
and (reset)
bound to F11 and F12 for easy reloaded workflow.
maybe if you have a fn which kicks off your tests but isn't picked up by the cursive integration you could bind it to a key this way?
awesome, thanks a lot!
@U0522TWDA The test markers are not all errors, they’re also the green checkmarks beside passing tests.
The last test action is the last one of “Run tests in current NS” or “Run a particular test” that you did. You can use it to repeat the last test(s) that you ran, whatever they were.
What I do for testing is to use Preferences | Appearance & Behavior | Quick Lists. I have one called “Testing” that contains Re-run last test action, Run test under caret, Run tests in NS, and Clear markers. Then I bind that to a key (Cmd-Shift-Space in my case) and when I use that key I get a menu, like this:
awesome ,thanks a lot for the tip!
@cfleming This issue doesn't specific to lein https://github.com/cursive-ide/cursive/issues/2173. This time the issue happens when I first open lein project, then I open deps project.
How to fix "Cannot apply parinfer due to inconsistent indentation"? How do I find the problematic line(s)?
What I do for testing is to use Preferences | Appearance & Behavior | Quick Lists. I have one called “Testing” that contains Re-run last test action, Run test under caret, Run tests in NS, and Clear markers. Then I bind that to a key (Cmd-Shift-Space in my case) and when I use that key I get a menu, like this: