Hello, Calva friends! I've been doing Clojure development using Calva on and off for about a year now and have never run across this issue. I'm using clj-time to work with dates/times. When I spin up a REPL by jacking-in, when using the clj-time.local namespace to get local-now, I am getting a date the represents the UTC time zone instead of my local time zone. Is this a REPL problem? A PBCK problem? Thank you for any information!!!! I'm using Remote development to an Unbuntu WSL instance.
Hi @brian.smith, happy to hear from you! Pretty sure it is not to do with the tooling. If you do some regular println testing with lein run
(or equivalent), you should be able to confirm wether that is the case or not.
I know I get all dizzy trying to figure timezone things out. Having struggled with that a lot in my work project recently. π
Thanks @pez, I appreciate you responding. I am sure it isn't a problem with the tooling, just my understanding of it.
FYI, Calva friends.
@brandon.ringe, about https://github.com/BetterThanTomorrow/calva/pull/981 clojure-lsp now has a way to disable all lints (clj-kondo and clojure-lsp new lint) https://clojure-lsp.github.io/clojure-lsp/settings/#diagnostics-linter π
Awesome! Thanks for letting me know.
@brian.smith Iβm one of the maintainers of clj-time
and Iβd recommend not using it, but using the built-in Java Time via interop or one of the Java Time wrappers listed in clj-time
βs README.
I thought I was going insane for a minute. Thank you for responding. All I've been attempting to do is to find the number of hours difference between two date-times...
Date/time stuff is hard and timezones doubly so.
Iβm exploring calva, and trying out some clojure-lsp features. Calls: Show Call Hierarchy
doesnβt work for me. Should it?
But when I execute Go to Definition
when I am already on the function definition, I do get a popup which shows call references.
Hmm, okay. I'll create a ticket to track this, since it seems to not work correctly atm.
Yes, it works properly on emacs:
We don't have any middleware related to that, but I also don't see those requests being made, which is strange. It's possible that feature was added in a newer version of the protocol, but our client uses an older version currently. We'll have to investigate.
yes, definitely that was added on latest protocol version, 3.16
Ah, that makes sense then. We'll need to upgrade