-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cider-doc cannot lookup Closure and other Clojurescript dependencies #203
Comments
Can you post here the relevant message exchange with nREPL? (see https://docs.cider.mx/cider/troubleshooting.html#debugging-the-communication-with-nrepl) |
Yes, but it doesn't say that much.
Cider-browse-ns won't find goog.dom either. |
My guess would be that this doesn't work for JavaScript sources, but I don't do ClojureScript myself and I don't remember much of the relevant code in Orchard at this point. Perhaps @arichiardi can shed more light on this. |
(moved from cider to Orchard) |
Expected behavior
Cider-doc should resolve symbols from dependencies such as Google Closure and attempt to evaluate their doc-string if no other source of documentation is available.
Actual behavior
Running cider-doc on the function goog.dom/createElement will give "symbol not resolved".
But that function has a valid, if somewhat crude, docstring that cider can evaluate with
(:doc (meta #'goog.dom/createElement))
or(clojure.repl/doc goog.dom/createElement)
which gives:As a comparison. Function meta is lookable with cider-doc. Which opens:
But evaluating
(meta #'meta)
says the function is located at :While
(meta #'goog.dom/createElement)
:Maybe the issue is finding it?
Steps to reproduce the problem
Create a figwheel-main cljs project and jack-in with cider. Import namespace goog.dom and lookup any of its functions with cider-doc.
Environment & Version information
CIDER version information
Lein / Clojure CLI version
Clj win-install-1.11.1.1149.ps1
Emacs version
29.0.50
Operating system
Windows 10
JDK distribution
P.S.
I don't know CIDER enough to decide if this is a bug or missing feature.
The text was updated successfully, but these errors were encountered: