core-typed

2025-04-29T15:19:43.124929Z

https://github.com/Olical/background-check this is pretty cool. @olical marked it as experimental

👀 1
❤️ 2
2025-04-29T17:39:56.576859Z

Nice. There should really be a built-in function to check namespaces that might have changed from last time the checker ran.

2025-04-29T17:41:28.866369Z

Great to see someone trying the malli integration. Probably the most compelling use-case at this point.

➕ 1
2025-04-29T17:54:47.099679Z

Probably the lowest hanging fruit I can help with is the printing and serializing of type errors. I need to define a data format for each kind of error.

2025-04-29T17:55:18.271169Z

I've been stuck on the caching logic for years, so I'll give myself a break there.

2025-04-29T18:08:40.518379Z

Also this tools.namespace-aware runner might be relevant https://github.com/typedclojure/typedclojure/blob/0b3ffb01b6a943bdfe0c279cfc7aae78304bec7c/typed/clj.checker/src/typed/clojure/main.clj#L146 What's missing is top-level configuration. We should have a standard typedclojure.edn file per project for things like the :background-check/ns-patterns configuration so it can be shared from multiple contexts

👍 1
2025-04-29T19:13:59.487889Z

This is cool. My suggestion would be to make it an LSP server for wider reach: https://github.com/Olical/background-check/issues/2 Regarding data format of errors, LSP https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnostic structure can beside location, code and message also include: • DiagnosticSeverity: Error, Warning, Information, Hint - are there kinds of type errors that might be just less severe hints? • CodeDescription URI with more information - this could point out to online documentation with more explanation about the kind of error • DiagnosticRelatedInformation - this can point to other locations in the code that could have contributed to the error

❤️ 1