vim/YouCompleteMe
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
6c9cdd7358
YouCompleteMe/python/ycm/tests/client/completion_request_test.py

219 lines
6.0 KiB
Python
Raw Normal View History

Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
# Copyright (C) 2015-2019 YouCompleteMe Contributors
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
#
# This file is part of YouCompleteMe.
#
# YouCompleteMe is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# YouCompleteMe is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with YouCompleteMe. If not, see <http://www.gnu.org/licenses/>.
Futurize pass + manual fixes
2016-02-27 19:12:24 -05:00
from __future__ import unicode_literals
from __future__ import print_function
from __future__ import division
from __future__ import absolute_import
Do not install aliases from future Installing aliases from python-future is unreliable and slow.
2017-03-09 09:57:27 -05:00
# Not installing aliases from python-future; it's unreliable and slow.
Futurize pass + manual fixes
2016-02-27 19:12:24 -05:00
from builtins import * # noqa
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
from nose.tools import eq_
Move test_utils to tests folder This remove the file from coverage.
2016-10-14 05:00:57 -04:00
from ycm.tests.test_utils import MockVimModule
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
vim_mock = MockVimModule()
Move client tests to the main tests folder
2016-10-19 18:24:38 -04:00
from ycm.client import completion_request
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
Update flake8 config
2016-03-06 12:13:43 -05:00
Futurize pass + manual fixes
2016-02-27 19:12:24 -05:00
class ConvertCompletionResponseToVimDatas_test( object ):
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
""" This class tests the
completion_request._ConvertCompletionResponseToVimDatas method """
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
def _Check( self, completion_id, completion_data, expected_vim_data ):
Refactor CompleteDone logic Move CompleteDone logic to the CompletionRequest class.
2018-03-26 21:22:31 -04:00
vim_data = completion_request._ConvertCompletionDataToVimData(
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
completion_id,
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
completion_data )
try:
eq_( expected_vim_data, vim_data )
Fix bare except statement Use Exception to catch all exceptions instead of a bare except statement.
2017-10-23 14:53:14 -04:00
except Exception:
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
print( "Expected:\n'{}'\nwhen parsing:\n'{}'\nBut found:\n'{}'".format(
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
expected_vim_data,
completion_data,
Futurize pass + manual fixes
2016-02-27 19:12:24 -05:00
vim_data ) )
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
raise
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def AllFields_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( 0, {
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'insertion_text': 'INSERTION TEXT',
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'detailed_info': 'DETAILED INFO',
'extra_data': {
'doc_string': 'DOC STRING',
},
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : 'INSERTION TEXT',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
'info' : 'DETAILED INFO\nDOC STRING',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': '0',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def OnlyInsertionTextField_test( self ):
self._Check( 17, {
'insertion_text': 'INSERTION TEXT'
}, {
'word' : 'INSERTION TEXT',
'abbr' : '',
'menu' : '',
'kind' : '',
'info' : '',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'dup' : 1,
'empty' : 1,
'user_data': '17',
} )
def JustDetailedInfo_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( 9999999999, {
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'insertion_text': 'INSERTION TEXT',
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'detailed_info': 'DETAILED INFO',
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : 'INSERTION TEXT',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
'info' : 'DETAILED INFO',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': '9999999999',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def JustDocString_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( 'not_an_int', {
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'insertion_text': 'INSERTION TEXT',
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'extra_data': {
'doc_string': 'DOC STRING',
},
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : 'INSERTION TEXT',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
'info' : 'DOC STRING',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': 'not_an_int',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def ExtraInfoNoDocString_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( 0, {
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'insertion_text': 'INSERTION TEXT',
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'extra_data': {
},
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : 'INSERTION TEXT',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'info' : '',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': '0',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def NullCharactersInExtraInfoAndDocString_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( '0', {
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'insertion_text': 'INSERTION TEXT',
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'detailed_info': 'DETAILED\x00INFO',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
'extra_data': {
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'doc_string': 'DOC\x00STRING'
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
},
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : 'INSERTION TEXT',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'info' : 'DETAILEDINFO\nDOCSTRING',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': '0',
Allows empty insertion text. This is useful for hints for example, whose purpose is information display solely.
2016-01-02 17:55:49 -05:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def ExtraInfoNoDocStringWithDetailedInfo_test( self ):
self._Check( '0', {
'insertion_text': 'INSERTION TEXT',
Allows empty insertion text. This is useful for hints for example, whose purpose is information display solely.
2016-01-02 17:55:49 -05:00
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'detailed_info': 'DETAILED INFO',
'extra_data': {
},
}, {
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'word' : 'INSERTION TEXT',
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'info' : 'DETAILED INFO',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
'user_data': '0',
Allows empty insertion text. This is useful for hints for example, whose purpose is information display solely.
2016-01-02 17:55:49 -05:00
} )
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
def EmptyInsertionText_test( self ):
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
self._Check( 0, {
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'insertion_text': '',
Allows empty insertion text. This is useful for hints for example, whose purpose is information display solely.
2016-01-02 17:55:49 -05:00
'menu_text': 'MENU TEXT',
'extra_menu_info': 'EXTRA MENU INFO',
'kind': 'K',
'detailed_info': 'DETAILED INFO',
'extra_data': {
'doc_string': 'DOC STRING',
},
}, {
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'word' : '',
'abbr' : 'MENU TEXT',
'menu' : 'EXTRA MENU INFO',
'kind' : 'k',
'info' : 'DETAILED INFO\nDOC STRING',
Disable Vim filtering Disable Vim filtering by setting the 'equal' field of completions to 1. This should speed up completion and reduce flickering.
2019-04-08 07:38:03 -04:00
'equal' : 1,
Support for additional FixIts on java completions Java completer can include FixIts which are applied when a completion entry is selected. We use the existing mechanism implemented for c-sharp to perform these edits using the CompleteDone autocommand. However, the existing mechanism relies on pattern matching the source to work out which item was completed. Vim patch 8.0.1493 introduces support for user_data on completion items, so when available we populate it with the completion array index of the item and use that to get the exact element that was selected. This is both a lot faster and a lot more accirate. Of course when applying these 'FixIts' we don't interrupt the user with confirmation or the quickfix list as this would just be annoying. If the server reports that an edit must be made, we just make the edit. This is achieved by adding a silent flag to ReplaceChunks.
2018-02-10 18:48:22 -05:00
'dup' : 1,
'empty' : 1,
Handle null characters in completion response The completion info field may contain null characters e.g. \x00 in Python docstrings. These characters cannot be evaluated so they are removed. Rewrite the function that convert ycmd completion to Vim completion.
2018-10-28 14:31:19 -04:00
'user_data': '0',
Show docs from clang completer in preview window We add the detailed_info (which is the function definiton) followed by the brief comment
2015-08-16 10:17:12 -04:00
} )
Reference in New Issue Copy Permalink