Fork me on GitHub
#cider
<
2023-12-14
>
hifumi12304:12:19

Latest CIDER (1.13.0-snapshot) seems to break CLJS autocomplete in general. Even in a barebones shadow-cljs project, I can no longer get meaningful suggestions when I type e.g. js/document.

vemv07:12:01

Weird, I think we'd have noticed but I'll make sure to check it out this morning

hifumi12308:12:07

for what its worth, CIDER 1.11 seems to work fine, so something in either 1.12 or 1.13 changed

👀 1
hifumi12308:12:40

here is what i get with the old CIDER, for instance

vemv08:12:48

looking at it now. I can repro that. However I can see this:

hifumi12308:12:48

as for the newer version of cider, …

hifumi12308:12:53

and all objects suggest these same properties, so there is effectively no autocomplete

vemv08:12:00

It might have been https://github.com/clojure-emacs/clj-suitable/pull/42 Is your issue limited to js/document ? What about general cljs vars and keywords?

hifumi12308:12:08

This happens with JS objects in general

hifumi12308:12:20

e.g. try js/goog.object and you will not see any of the goog.object functions

vemv08:12:02

Ok, can you confirm the issue doesn't happen for cljs vars and keywords?

hifumi12308:12:20

ClojureScript autocomplete works fine, its just the JS objects with issue

hifumi12308:12:21

here is comparison of old and newer CIDER for js/goog. just to demonstrate the JS autocomplete issue

vemv08:12:54

Nice, appreciated. It's very likely that PR. I'll try to limit its effect to String , as originally intended

hifumi12308:12:20

Thanks! I’ll also note that javascript autocomplete does work for showing “top-level objects”, as in your screenshot. The problem happens once you try to get suggestions for fields and methods of objects

👍 2
hifumi12300:01:27

Any updates? I’m still facing this problem with the latest version of CIDER

vemv05:01:31

Sorry, it escaped my mind but today it won't https://github.com/clojure-emacs/clj-suitable/issues/45

gratitude 1
vemv12:01:40

I'm aiming for a release by the end of the week https://github.com/clojure-emacs/clj-suitable/pull/46 including misc other stuff

vemv07:12:09

ℹ️ 🎉 I have interesting news to share: Clojurists Together clojurists-together is awarding 9k to CIDER, this quarter. With that I'll be able to focus 100% of my time on all things CIDER for a while, in a similar way that I did for a remarkable number of months this year. You can read about my ongoing collaboration with @bozhidar https://www.clojuriststogether.org/news/july-and-august-2023-long-term-project-updates/#ciderrepl-bohzidar-batsov. If you wish to amplify this impact, possibly securing one or two extra weeks of focused work, kindly consider making a one-off donation to our https://opencollective.com/cider, or pitching so to your organisation.

cider 17
🎉 15
clojurists-together 5
mikerod20:12:07

Can I disable cider asking me if I want to open the browser URL after cider-jack-in-clj&cljs. I don’t want the prompt or to open the browser.

vemv20:12:43

Have you tried searching its wording in the cider repo? It's what I'd do 🙂

mikerod21:12:52

It’s a bit of an annoying search string:

Visit '' in a browser? (y or n)
Where the port varies. I can dig though if needed. I just wondered if there was something more readily available in docs that I didn’t see.

mikerod21:12:14

A lot of times, I just end up navigating the source of the jack-in command until I find where it happens.

mikerod21:12:46

found it though I think cider--offer-to-open-app-in-browse.

mikerod21:12:43

and found the var.

mikerod21:12:48

cider-offer-to-open-cljs-app-in-browser

🙌 2