This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-26
Channels
- # announcements (28)
- # asami (13)
- # babashka (10)
- # beginners (170)
- # boot (1)
- # calva (35)
- # cider (21)
- # circleci (13)
- # clara (6)
- # clj-http (1)
- # clj-kondo (29)
- # cljdoc (5)
- # clojure (89)
- # clojure-czech (2)
- # clojure-europe (20)
- # clojure-france (16)
- # clojure-nl (6)
- # clojure-uk (5)
- # clojurescript (80)
- # community-development (6)
- # conjure (13)
- # cursive (18)
- # datascript (9)
- # datomic (1)
- # duct (1)
- # gratitude (2)
- # helix (7)
- # jobs (2)
- # kaocha (3)
- # lsp (22)
- # malli (5)
- # meander (1)
- # other-languages (34)
- # pathom (18)
- # polylith (24)
- # quil (10)
- # re-frame (5)
- # releases (1)
- # remote-jobs (4)
- # reveal (7)
- # shadow-cljs (8)
- # tools-deps (53)
stupid question, but why does formatting require running the clj-kondo analysis?
We could make format just check all cljc files in folders but I think would be a adhoc approach different how almost everything on clojure-lsp works
yeah I see
I would have thought that formatting is a context-free operation let's say, it could even just know about a single namespace and reformat it
I've done a big round of reformatting on all our projects, and would like to just say to run that before commiting or something, but given how long it takes that's not really feasible
@ericdallo LSP seems to incorrectly show the following documentation:
(defn wrap-hl-req-res-model
"Middleware that converts Ring Request/Response model to Holy Lambda (AWS Lambda) Request/Response model.
Ideal for running regular ring applications on AWS Lambda.
Middleware supports both `sync/async` ring handlers.
**Example**
clojure
(ns core
(:require
[fierycod.holy-lambda-ring-adapter.core :as hlra]
[fierycod.holy-lambda.core :as h])
(defn ring-handler
[request]
{:status 200
:headers {}
:body \"Hello World\"}
(def HttpApiProxyGateway (hlra/wrap-hl-req-res-model ring-handler))
(h/entrypoint [#'HttpApiProxyGateway])
"
[handler]
(fn
([request]
(ring-response->hl-response (handler (hl-request->ring-request!! request))))
([request respond raise]
(handler (hl-request->ring-request!! request)
(fn [response] (respond (ring-response->hl-response response)))
raise))))
Here is the repro 🙂
I can't repro that, where exactly are you calling the docs command? what line and column exactly?
You can repro that. See ns :d
And ring response :D
Only dracula btw <3
this seems like a lsp-ui
bug since showing the docs via eldocs with doom works perfectly for me (`K`)
feel free to open an issue on lsp-ui , it's probably related with the way it renders markdown on the popup
Ohh. Sure. I will
Thank you @ericdallo