Possibly broken support of ClojureScript in Cursive 1.1.0-14.1 (lots of "X cannot be resolved" warnings, no navigation)
Summary: Create a new CLJS project, open it with Cursive/IntelliJ and see that none of CLJS symbols can be resolved.
Prerequisites:
- Cursive 1.1.0-14.1
- Leiningen 2.5.3
- IntelliJ 14
- JDK 1.8
- OS X 10.9
Steps to reproduce:
- $ lein new mies-om demo
- Launch IntelliJ, choose "import project", chose "demo/project.clj", say "next" to all questions
- Wait for all background tasks to finish
- Open "src/demo/core.cljs"
- Observe that the following symbols are not resolved:
- enable-console-print!
- js/document
- getElementById
NOTE: Doing "File -> Invalidate Caches / Restart ..." has no effect
@cursive-ide, any progress on this? We are using quiescent, and Cursive (1.1.0-15) is not resolving any of the quiescent macros. Reproduce:
- Check out: https://github.com/levand/quiescent/tree/release/examples/animations
- Open src/animations.cljs in Cursive
- Observe all the uses of defcomponent, div and "regular" cljs calls are not resolved
@cursive-ghost Are you not going to fix any issues with ClojureScript anymore, since you removed the CLJS tags from all issues in 2023?
@nhooey No, that's definitely not the case - I removed all feature tags from all issues, since it was confusing.