You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, if you type a space (as shown above, to have whitespace between : and the value), the completion list gets filtered and disappears. While it's possible to set <space> as a trigger character, that results in the completion provider being called a lot (for example on every space inside comments) which then need to be filtered out by the extension.
Is it reasonable to ignore leading whitespace when filtering the completion list to simplify things? It seems almost certain that no provider is ever going to return completion items with leading spaces expecting them to be precisely filtered?
The text was updated successfully, but these errors were encountered:
We have a great developer community over on slack where extension authors help each other. This is a great place for you to ask questions and find support.
Given a language that takes named args with colons:
It seems sensible to set
:
as a trigger character to open completion. This works fine:However, if you type a space (as shown above, to have whitespace between
:
and the value), the completion list gets filtered and disappears. While it's possible to set<space>
as a trigger character, that results in the completion provider being called a lot (for example on every space inside comments) which then need to be filtered out by the extension.Is it reasonable to ignore leading whitespace when filtering the completion list to simplify things? It seems almost certain that no provider is ever going to return completion items with leading spaces expecting them to be precisely filtered?
The text was updated successfully, but these errors were encountered: