Now I'm shipping JARs to Clojars and have provided a mechanism to support Clojure CLI and lein through a per-repo script, a bit like how Kaocha integrates into your project. This gives you the flexibility to support it in different kinds of projects as well as run different versions of this LSP per project. This should help with any breaking changes in the type system in the future where some projects might still need to migrate etc. Please let me know if you get this working with leiningen though, I haven't proved it end to end yet but had it working with Clojure CLI. I have the LSP working under Lein, just no good typed code under a lein project right now to test with is all.
Please see the readme for the recommended LSP client config and example scripts to start the server. If you get this working in VS Code please add it to the docs! Maybe we need to ship a VS Code plugin?
I'm struggling to release Typed Clojure 1.4.0 because I'm migrating to tools.deps from maven. I want a stable version available for typedclojure-lsp to depend on.
I want to test typedclojure-lsp but I'll concentrate on that first.
It's a real headache.
I like the readme example. No runtime dependency on Typed Clojure 👌
Nope! It's just a tooling thing, and the user could also just depend on malli for their runtime checking + have it checked statically thanks to the integration.
Exactly why I like it. Malli is much much better at runtime checking, and there's no reason TC should be on the classpath for releases.