microsoft / microsoft/TypeScript-Sublime-Plugin

Sublime suggestions appear despite auto_complete_api_completions_only set to true

Open
#777 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.7k
Forks
236
Avg merge
21d 13h
Merged PRs (30d)
1

Description

Since Sublime build 4073 (changelog includes "Reworked Auto Complete UI"), the setting auto_complete_api_completions_only doesn't do anything for me anymore, showing content-based completions along with TS ones regardless.

I have fiddled with the plugin code and it seems that sending sublime.INHIBIT_WORD_COMPLETIONS instead of sublime.INHIBIT_EXPLICIT_COMPLETIONS in typescript/listeners/completion.py fixes the problem.

Should INHIBIT_WORD_COMPLETIONS be used when auto_complete_api_completions_only is on?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in typescript/listeners/completion.py and reproduce the behavior with auto_complete_api_completions_only enabled in Sublime build 4073 or later. Compare the completion inhibition behavior described in the issue and confirm that the setting prevents content-based completions while retaining TypeScript completions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.