This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-29
Channels
- # announcements (8)
- # aws (34)
- # beginners (92)
- # calva (19)
- # capetown (1)
- # cider (10)
- # cljs-dev (7)
- # cljsrn (11)
- # clojars (7)
- # clojure (130)
- # clojure-europe (4)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (11)
- # clojure-russia (1)
- # clojure-spec (4)
- # clojure-uk (64)
- # clojurescript (51)
- # cursive (9)
- # data-science (6)
- # datomic (29)
- # emacs (3)
- # figwheel-main (14)
- # fulcro (4)
- # graphql (3)
- # jackdaw (2)
- # jobs (4)
- # kaocha (17)
- # leiningen (3)
- # luminus (1)
- # off-topic (46)
- # pedestal (6)
- # portkey (2)
- # re-frame (6)
- # reagent (1)
- # reitit (9)
- # shadow-cljs (9)
- # sql (10)
- # yada (6)
I made a PR to orchard so that `cider-browse-spec´ can expand ns-aliased keywords https://github.com/clojure-emacs/orchard/pull/42
Got a quick question about hot reloading functionality. I think that it still should be a part of clj-refactor. Why? 1. Clj refactor can use the hot reload functionality when adding the library so the user experience will be much more pleasant. 2. Hotreloading was a part of clj-refactor since the beginning so it should be still there 3. In order to make the user experience smooth I would have to copy and paste the existing functions from clj-refactor. (I mean those which touch adding dependencies) What is your opinion guys?
i thought the discussion was whether it should go into CIDER or clj-refactor. None of those positions argue about where it should live, they just seem to argue that the feature should exist
The question is where the feature should land. Should I put it in clj-refactor?
@dpsutton Do you know how I can add the library with specific hash commit? I wanted to add tools.deps.alpha on jack in but the thing is that for instance leiningen does not allow hash commit as a version of dependency. What I plan to do is simply wrap the call to ’add-lib with emacs-lisp.
@kwcharllie379 I'd argue for it going into CIDER. Hot-loading of dependencies is not really a refactoring task to me. (Along similar lines, I'd argue for separating the functionality of hot-loading a dependency in the running process from the functionality of updating projects.clj
or deps.edn
to add that dependency--the latter fits more with the spirit of clj-refactor, IMO. I would love to be able to hot-load dependencies without my project files being modified.
I see your point @enn. The case is that if I move the code to cider regarding the hot-load functionality I would then have to move a lot of functions from clj-refactor to cider as well.
I would rather avoid it for now