AI Code Completions
This is the repository for the backend of TabNine, the all-language autocompleter. There are no source files here because the backend is closed source.
You can make feature requests by filing an issue. You are also welcome to make pull requests for changes to the configuration files.
languages.ymldetermines which file extensions are considered part of the same language. (For example, identifiers from
.cfiles will be suggested in
language_tokenization.jsondetermines how languages are tokenized. For example, identifiers can contain dashes in Lisp, but not in Java.
If your feature request is specific to a particular editor's TabNine client, please file an issue in one of these repositories:
You may be interested in these TabNine clients written by third parties:
NOTE: Codota is not validating any code in those plugins and is not responsible for them by any means. - Emacs - Vim (Deoplete) - Eclipse - Your client https://github.com/codota/TabNine/blob/master/HowToWriteAClient.md
If new features don't work for you, check that you have the most recent version by typing
TabNine::versioninto your text editor. If you don't have the most recent version, try restarting your editor.
.dextension are now recognized as D source files (closes #56).
-in identifiers when parsing Racket code.
\d.*[a-zA-Z].*\d.*[a-zA-Z]from the project index. This is supposed to prevent long keys or base64 literals from occurring in autocompletion suggestions. The tokens are not filtered from the directory index or the file index.
.tsxfiles as TypeScript rather than
foo(it will additionally insert
)to the right of the cursor once the suggestion is accepted). The editor clients do not support this yet as it requires an upgrade to the communication protocol with TabNine; this is coming soon. Closes #11 as this is no longer an issue with the TabNine backend.
.git. This permits nested Git repositories (closes #5).
.tabnineignorefiles (closes #15).
TabNine::disable_auto_updateinto your text editor (closes #14).
TabNine::config_dirto see where config files are being stored.