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
After installing these wonderful snippets, they are now being suggested almost everywhere (except when using the 'dot-into' operator on a type), such as when trying to list the properties of an object.
Where I noticed it was when "ctrl+space listing" the properties of the @Component metadata object.
What I concretely did was to use the ng2-controller template to create a new controller. Then, because I am new to AngularJS, I moved the keyboard cursor into the argument object of the @Component call to see what else (except for moduleId, selector and templateUrl) was available there. So I hit "ctrl+space" and was overwhelmed with the code templates also showing there, where I guess, they would not be valid.
The text was updated successfully, but these errors were encountered:
We don't expose scopes/context that is derived from a TM grammar because of their varying qualities and because that would lead to feature that are tight coupled with one specific grammar.
For smarter snippets we recommend to implement a CompletionItemProvider which for instance can use a syntax tree to figure out what the best snippets for a certain position are. The drawback however is that those snippets are computed dynamically cannot be invoked from tab-completion (yet)
After installing these wonderful snippets, they are now being suggested almost everywhere (except when using the 'dot-into' operator on a type), such as when trying to list the properties of an object.
Where I noticed it was when "ctrl+space listing" the properties of the
@Component
metadata object.What I concretely did was to use the
ng2-controller
template to create a new controller. Then, because I am new to AngularJS, I moved the keyboard cursor into the argument object of the@Component
call to see what else (except formoduleId
,selector
andtemplateUrl
) was available there. So I hit "ctrl+space" and was overwhelmed with the code templates also showing there, where I guess, they would not be valid.The text was updated successfully, but these errors were encountered: