cider

Expected behavior

I often need to connect to both a clj nrepl server as well as a shadow-cljs nrepl server for full stack dev. Because the clj nrepl server prints its port to .nrepl-port, and shadow prints its port to .shadow-nrepl/nrepl.port, ideally their respective ports should both be automatically discoverable when I try to connect via cider-connect.

Actual behavior

If a

Describe the Bug

The band 'Between the Buried and Me' scrobbles as 'Between The Buried.' Doesn't happen on other Apple Music clients that also have scrobbling.

Steps to Reproduce

1. Play any track from the band

Environment Information

• OS: Windows 10 Home 19044.146

The documentation of the retest command doesn't seem correct.

Return exception cause and stack frame info for an erring test via the stacktrace middleware. The error to be retrieved is referenced by namespace, var name, and assertion index within the var.

The [Cider docs say this](https://docs.cider.mx/cider/testing/test_repo

Currently the eldoc type is either function or variable:

(defn- extract-eldoc
  [info]
  (if-let [arglists (seq (-> info extract-arglists format-arglists))]
    {:eldoc arglists :type "function"}
    {:type "variable"}))

This means that the result users see is not particularly accurate, not to mention that the function check is pretty primitive. We should add types like `m

Project should include more examples or case studies in documentation.

Ideas:

• a complete E2E pipeline using all of xcodebuild, altool, and Cider
• examples of more complex configuration files
• an example of how you could use a dedicated metadata repo, when coupling to your app repo is impractical.