This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-09
Channels
- # aws (4)
- # bangalore-clj (1)
- # beginners (94)
- # boot (19)
- # cider (42)
- # cljs-dev (21)
- # cljsrn (4)
- # clojure (142)
- # clojure-austin (10)
- # clojure-greece (25)
- # clojure-italy (14)
- # clojure-russia (14)
- # clojure-serbia (13)
- # clojure-sg (6)
- # clojure-spec (74)
- # clojure-uk (69)
- # clojurescript (236)
- # consulting (1)
- # cursive (26)
- # data-science (6)
- # datascript (2)
- # datomic (31)
- # editors (5)
- # emacs (24)
- # funcool (5)
- # hoplon (8)
- # jobs-rus (1)
- # luminus (12)
- # lumo (17)
- # off-topic (90)
- # om (45)
- # onyx (5)
- # pedestal (2)
- # powderkeg (12)
- # protorepl (2)
- # re-frame (30)
- # remote-jobs (2)
- # ring-swagger (17)
- # rum (46)
- # slack-help (1)
- # test-check (2)
- # yada (62)
It finally went away but it left all my Datomic functions as unresolved. Though, I stopped working in that project and just took a peek at the project and it seems to have magically fixed itself.. Maybe IntelliJ's indexing was pretty delayed or something?
There's still no Cursive for 2017.2, right? Just checking since I had another machine prompt to update, and I'm not sure how to tell what plugins will be invalidated after an update …
hagmonk: AFAICT if you install Cursive before upgrading to 2017.2 it continues to work fine. If you install 2017.2 and then try to install Cursive, it won’t let you. wrong
@U3DAE8HMG I’d be surprised if that worked - IntelliJ should prohibit the current Cursive version from working in 2017.2
I installed 2017.2 on my personal machine and noticed it wouldn’t allow me to install Cursive, but for some reason I thought I was running 2017.2 on my work machine
@hagmonk No, sorry - I’m working on fixing a bug, hopefully I’ll get the EAP out today.
@kenny There’s at least one bug there I’m planning to investigate for the next build.
@cfleming I'm refactoring some cljs code where have to turn some fn calls to macro calls. So far I've been using "Replace in path" with regex. It actually works pretty well
So then I thought maybe structural replace would be pretty simple to implement for CLJ. But not sure if that option would be used by a lot of people.
One of the biggest pain point for me is that there is no automatic imports of "refer'd" vars.
@rauh Yeah, I’m planning to add that soon as part of more sophisticated ns refactoring in general.