Fork me on GitHub
#cursive
<
2024-05-08
>
roklenarcic10:05:54

I’ve got many deps projects in folders named common. When I do the deps refresh it tries to create many duplicate modules called common which intellij doesn’t allow, so the build fails. Also when I try to import modules manually I cannot pick module name. So even if I want to change module name on import to avoid collisions, I cannot.

cfleming22:05:52

Cursive should create unique names for those modules, I’ll double check that that is working and get back to you.

roklenarcic11:05:40

Also if I manually rename a module from common to common-build , every time I refresh deps projects page, it will rename it back to common.

DenisMc14:05:28

Hi, I have a problem with my cursive setup, polylith, and babashka. I have a polylith project, with a base (root) deps.edn, which contains the various test paths of the components in the project under :aliases{test{:extra-paths […]}}. Within each deps.edn for each component, I again have a :test alias defined, with :extra-paths defined simply as ["test"] (this corresponds with the setup for example in https://github.com/furkan3ayraktar/clojure-polylith-realworld-example-app, which shows a simple polylith project with correct structure). All well and good, and all works fine - except, I also have a babashka module in the project. When I go to File->Project Structure->Project Settings->Facets, and go to add the babashka facet to the relevant module - and then click Apply, I get an error saying Cannot Save Settings - Module '<my root module>' must not contain source root 'path/to/component/test'. The root already belongs to module <component module in question>. Any ideas about what might be going on here?

DenisMc14:05:27

Rubber ducking FTW. The problem was that I had the test alias enabled in my Clojure Deps settings, once i removed that (keeping just dev and poly ), the error resolved.

👍 1
Nikolas Pafitis19:05:35

Since the latest Intellij update, my code is formatted funny without colors. I checked the color scheme in the settings and it's all good there. but this is how it shows. Does anybody know what might be the issue?

Nikolas Pafitis19:05:27

I ended up downgrading to the older version and that fixed my issue. Couldn't figure out what setting was causing the code to be gray formatted.

manutter5119:05:36

Check your cursive license and make sure it's still current for the version you want to use? I had a similar experience once when I let my license lapse accidentally.

Nikolas Pafitis20:05:31

I'll check tomorrow if my license expired.

👍 1
cfleming22:05:41

Your Cursive licence won’t affect this, licences are perpetual and just don’t get updates if they’re out of their update period. And either way, Cursive never disables features for licensing reasons, it just nags.

cfleming22:05:56

I have no idea what might be going on there though, I’ve never seen that.

imre09:05:47

Just OOC, what were the two IJ versions referred to?

salam14:05:25

this might be related to an ongoing (but supposedly fixed) issue with IntelliJ IDEA itself: https://youtrack.jetbrains.com/issue/IJPL-28967

cfleming23:05:19

Thanks salam, I’ve experienced that one, glad it’s (allegedly) fixed.

salam21:06:06

i saw this happen to me again today: good code is grey. they reopened the issue i posted above.

cfleming21:06:51

Yes, I’ve seen it since that release too, I’ve voted for that issue.