Clojurians Log v2

https://clojurians.slack.com/archives/CPABC1H61/p1772444066646999 Maybe that is a good reason to check them in

We're trying to figure out what to do. My stance is that checking in parts of dependencies that we already specify to a specific version in deps.edn should be unnecessary. It opens up for having library versions out of sync with their own linting rules.

If they are out of sync they will be overwritten

By what? the import-configs script?

by clojure-lsp or a manual import

it's not an ideal situation. the ideal situation would be to load stuff directly from the classpath I guess. something I want to look into

but for inlined configs that would be difficult since the config is hidden in between the code

I had expected lsp to do this, hence my question. Another option is to write a git-hook that runs the import when deps.edn changes

clojure-lsp should be doing this. but maybe you first have to restart your workspace, it's not common to run init stuff on a file change I think

if you're using emacs, it's lsp-workspace-restart if you're using lsp-mode

We're all using the same Emacs setup 😄

https://github.com/magnars/emacsd-reboot/

lsp-workspace-restart works, but must be run manually

So we're looking for some way to make it happen automatically - but only when needed, since it takes some time.

since you're using the same emacs config, I could imagine a way to script this in emacs. take the hash of deps.edn, when it changes, run lsp-workspace-restart?

this could create problems when you're actually editing deps.edn though, so not sure about the UX

True, we could just do it in Emacs. I had originally planned to do it after pulling/committing, so that should solve the UX bit.

after pulling/committing could be done with a git hook

Full circle 😄

We ended up with a hook from our (start) function. Thanks for the assistance, @borkdude! 🙏

🙇