-
Notifications
You must be signed in to change notification settings - Fork 281
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
Fix #515 don't ignore LSP client's snippet support capabilities #526
Conversation
Thanks for your interest in palantir/python-language-server, @Shougo! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request. |
Please test it. |
Tested it, works fine |
Really looking forward to this merge |
I have fixed unit tests. |
ping @palantirtech |
I think this pr should be merged. |
ping @gatesn |
Apologies, I've been out on vacation. For expediency, I've made a few changes to this PR here: #529. Namely, the jedi setting for enabling snippets doesn't override what client capabilities say; and snippets are only generated for positional arguments. |
OK. |
This is the way python-language-server used to work before palantir#519. This shouldn't conflict with the goals of palantir#515 of palantir#526, i.e. if the client does _not_ declare support for snippets, none are sent. * pyls/plugins/jedi_completion.py (pyls_completions): Default should_include_params to True, like before.
Fix #515