-
Notifications
You must be signed in to change notification settings - Fork 263
Snippet completion before object completion #465
Comments
TypeStrong/atom-typescript#353 |
Reopening as this is an issue with all providers. Not sure what the best way to mix providers is quite yet. |
Oh, okay. |
@benogle: This is why we had provider blacklisting 😄. It was removed, for good reason, and to simplify |
We have the equivalent of the blacklisting now with the inclusionPriorities. There is no compositing of separate providers. IMO, this is about mixing them together in a reasonable way, and not about not returning providers results. Every provider will have this issue mixing in with the snippets. |
@benogle the old implementation allowed one provider to explicitly blacklist another provider for the scopes within which it operated. Now, that would have been extremely flakey because it relied on the But in concept, a provider author might declare its priority to be 1, and the say "except, I should always appear above autocomplete-snippets suggestions". Even that approach feels dirty though. I think a solution may lie in a combination of the following:
|
+1 really affect usability. The intended behavior is achieved by disabling |
@elliotaplant Same.. my custom scoped snippet should IMO always take priority.. at the very least when i type all the prefix characters: |
@leroix want to take a look at this one? |
I'm actually not sure where this needs to go, either atom-typescript, Atom itself, or here.
Since the update Atom did to
![image](https://cloud.githubusercontent.com/assets/2054218/7671281/2e356e28-fc7d-11e4-95f0-0997f6a77841.png)
![image](https://cloud.githubusercontent.com/assets/2054218/7671283/45d797a4-fc7d-11e4-9073-fb12122b9a89.png)
v0.199.0
snippet completions come before object completions, which shouldn't be popping up at all in the context of the completion.This is particularly annoying because it completely negates proper completions, especially in the second image where it completely hides the
info
method from being accessible.Again, I'm not sure if this is an Atom, TypeScript, or Autocomplete issue.
Thanks.
The text was updated successfully, but these errors were encountered: