-
Notifications
You must be signed in to change notification settings - Fork 38
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port the cljs-tooling completion machinery to compliment #62
Port the cljs-tooling completion machinery to compliment #62
Conversation
I'm extremely excited about this and will be hooking it into my prepl neovim tooling immediately. If I get around to it quickly enough I'll try to provide feedback and improvements where applicable. |
@Olical thank you! Note that this isn't working at the moment, I didn't have time yet to port the most important piece 馃槈 |
6283469
to
097f17a
Compare
097f17a
to
f673962
Compare
Waiting for this on some feedback on #63 - the solution I have with dynamic vars is not really ideal imho |
Ok pushed the version with the dynamic var. I have also a question: given that Clojure and ClojureScript completions are mutually exclusive (for instance I get Or maybe cider should configure that from the outside |
99859e9
to
245f7ba
Compare
@alexander-yakushev during Clojure/North I got to a mostly usable version of the port. I am missing still the In any case, maybe a second run of review would be good. Please remember that this is only 30% my code. Now I understand it completely, but the I am hoping others and myself to give it more love over time when it's in |
cb64a3d
to
f612191
Compare
f612191
to
047eda2
Compare
Added the A review now would be awesome. |
047eda2
to
ad167dc
Compare
pingy-ping 馃敂 |
I've skimmed through it. It looks pretty good!
I've needed this before as well but there is yet no way to do it. Is it necessary for this PR? If not, I might be able to think about it again later and maybe come up with something. |
How the tests should be run with these changes? When I plainly run |
Yes you need to add the profile (in Try:
|
Sorry, missed that. Yes, that works. |
I was thinking really that if the goal is to have the exact same api (I looove fuzzy completions) it might be maybe a better idea to include the correct broken-down Cljs implementations inside the current ones. Meaning, a conditional on the presence of the dynamic var Either that or to use/share the pieces of code from the Clojure completions that do fuzzy matching in the ClojureScript namespace. Does it make sense? |
ad167dc
to
7d92711
Compare
Comments addressed. |
7d92711
to
ae4d775
Compare
It seems the word :deprecated has other candidates matching so this change is necessary to keep the validity of the tests.
Alright chums, let's do this! |
馃槺馃帀馃帀馃帀 I'll be trying this in Conjure ASAP! |
Happy this is in now! But please let's keep in mind that I have a better (kinda breaking) improvement.. |
@alexander-yakushev it would be awesome to release a beta or snapshot version so that I can try it out in |
Already did, |
Great thank you! |
This PR shows what CLJS completions look like.
The code is ported from
cljs-tooling
- what is used by Cider for ClojureScript completions.The goal here is to end up with the same public api and behavior. Probably some
of the Compliment options would not apply in which case, please, advice 馃槃
I am always open to tweaks of any sort, just send any feedback over.