-
Notifications
You must be signed in to change notification settings - Fork 111
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
QA for latest changes #500
Comments
As a pereliminary diagnostic, this is part of the user error report I got (using clj-refactor.el master, latest)
It seems to have to do with Would love if someone could just give a QAing / debugging session and weed out various unforeseen cases for this conditional: clj-refactor.el/clj-refactor.el Lines 2018 to 2027 in 9e1f920
I'd say it's easier than it sounds! |
I can give the latest 3.0.0 refactor-nrepl a go next week, but from the traceback it just looks like a missing type check in (defun cljr--in-keyword-sans-alias-p ()
"Checks if thing at point is keyword without an alias."
(let ((sym (cider-symbol-at-point)))
(and
+ (stringp sym)
(cljr--keywordp sym)
(not (string-match-p "::.+" (cljr--symbol-prefix sym)))))) I wonder if this will solve it. |
Thanks! Sounds likely, looking forward to your session |
👋 Any luck with the QAing? |
Update, the error two users facing was clojure-emacs/parseclj#35 so there isn't necessarily a bug on clj-refactor/refactor-nrepl's end |
Yup, I've been using the latest refactor-nrepl and clj-refactor.el all week (including cljr-slash) without any issues. |
Thanks! Between that and clojure-emacs/cider#3072 I don't fear anymore about these features working properly. |
I've got a couple reports that cljr-slash is not working for the latest versions of refactor-nrepl + clj-refactor.el.
When I tried to debug with those users, the backend part seemed in order e.g.
(refactor-nrepl.ns.libspecs/namespace-aliases)
returns a proper map. There's a good deal of unit-testing in refactor-nrepl anyway.I don't know so much about clj-refactor.el though. I have barely performed changes to it yet. I see in the commit log
cljr-slash
got bit of a revamp earlier this year.I use an old version of clj-refactor.el and have it hard to use $latest I believe. So whenever I QA things, what I'm trying out is refactor-nrepl (official, latest) + my clj-refactor.el (old, divergent). So it's not exactly realistic QAing.
I wonder if someone in the team would have the time to give the latest refactor-nrepl + clj-refactor.el versions a go? @expez @magnars @yuhan0
🍻 - V
The text was updated successfully, but these errors were encountered: