Fork me on GitHub
#cider
<
2024-04-18
>
oyakushev09:04:56

Does CIDER still support Clojure 1.8 officially or semi-officially? I see that both orchard and cider-nrepl test against 1.9 the lowest, but there are still some 1.8 compatibility warts in the code.

vemv12:04:49

> 1.8 compat, while it was intended to be, was broken for a possibly very long time. https://github.com/clojure-emacs/cider-nrepl/pull/840

👍 1
vemv16:04:00

Tip 💡 in case it makes someone's day - nowadays in AWS/GCP it's fairly easy to do structured logging with something like https://github.com/viesti/timbre-json-appender . Then you can gcloud logging read blah to get these JSON logs for a given timespan, and trivially read them into Clojure data structures to be fed into the CIDER Inspector. And there you have it - rich production log inspection from the comfort of Emacs. It sure has 10x'ed my ability to diagnose prod issues.

clojure-spin 5
🪵 4
1
vemv16:04:02

The timbre/with-context+ (or 'MDC' outside the Timbre world) macro plays well with this technique - more context, more data, more inspection

Oliver Marks18:04:34

Curious if there is a way to configure which deps.edn is loaded, my understanding is that when you jack-in cider moves up the file tree looking for the first deps.edn file the issue with this is if you use polylith it has a deps higher up the file tree which is the one you usually want to jack into. you can work around this by jacking into a cljs file from the development but I often forget so curious if there is a way to override via dir-local or something ?

vemv18:04:05

You could advice-add :before the cider-jack-in function (or any of its cousins) so that it changes the default-directory to (vc-find-root) It should be possible to add that to .dir-locals (or to .dir-locals-2 if you don't want to pollute peers)

Oliver Marks19:04:34

ah nice idea I had not thought of solving it in elisp, thanks for the suggestion 🙂

🙌 1