-
Notifications
You must be signed in to change notification settings - Fork 7
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
Handle string requires gracefully #22
Comments
Just ran into this, although I'm not using shadow-cljs. ClojureScript's Library Property Namespaces can require string requires as well. |
Released |
Whoops, sorry, it's not as easy as bumping that dep isolatedly. We have to cut a cider-nrepl release that uses the new |
@vemv is there a way to override the version of |
Not directly, however we can release cider-nrepl which you could refer to in cider.el Relatedly, @bbatsov WDYT of making this defconst a defcustom instead? https://github.com/clojure-emacs/cider/blob/adfc1c940d452ace7d1dbea543024d422f60364c/cider.el#L409 Maybe we can split it into two as you mentioned earlier today. (I'd suggest not introducing a micro breaking change with it) |
Btw, constants in Elisp are not really constants - you can set this to whatever you want in your setup. And yeah - I'll likely add a defcustom for the injected cider-nrepl version. |
Just made the necessary changes - see |
Fix finally available in |
@vemv just tried it out and it's working great. Thanks for all your work on this. |
Very happy to read that! 🍻 |
Context
https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive/topic/cider/near/251080205
Brief
clj-suitable/src/main/suitable/compliment/sources/cljs/analysis.cljc
Line 259 in 223f890
Suggestion
If a
ns
is a string, instead of computing(meta (clojure.core/find-ns ns))
, return{}
.Similar for any other place where "string requires" might be handled throughout the codebase
...Obviously, ideally clj-suitable would understand the "string requires" and offer actual functionality for them. Not sure if that's at hand though. So it seems sensible to at least avoid a hard failure.
The text was updated successfully, but these errors were encountered: