-
Notifications
You must be signed in to change notification settings - Fork 177
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
dynamic cljs completions with suitable #633
Conversation
[msg cljs-env ns prefix extra-metadata] | ||
(concat (cljs-complete/completions cljs-env prefix {:context-ns ns | ||
:extra-metadata extra-metadata}) | ||
(suitable/complete-for-nrepl msg))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does suitable
need the entire msg
? I'm asking mostly because it seems to me that all the other params should be enough to get candidates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It needs access to the cljs options + repl env + compiler env. We can pull those out and just pass them along but it seemed simpler to hand in the msg.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. As this is something minor I guess there's no need to fret over it too much.
We should also mention this in the changelog, as it's certainly a noteworthy change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This patch looks great!
I would use another name though for the namespace. cljs-complete
is/will be already included in compliment
and suitable
will be providing js-objects
completions only.
I see one day all the functionalities being merged in compliment
tbh...
What exactly do you mean? |
I guess he meant the |
Well yes you are right, I can actually change it with my integration PR or something |
I meant the function name but no probs, it can be tuned later on. |
Before submitting a PR make sure the following things have been done:
Keep in mind that new cider-nrepl builds are automatically deployed to Clojars
once a PR is merged, but only if the CI build is green.
If you're just starting out to hack on cider-nrepl you might find
this article and the
"Design" section of the README extremely useful.
Thanks!