Semantic snippets: don't provide snippets when dotting of a type name

[DoctorKrolic]

Fixes: https://youtu.be/V_eRvgl5sVg?t=2190

[DoctorKrolic]

@akhera99 PTAL on this simple fix

[MartyIX]

Is there any documentation for semantic snippets that would explain how the feature work? Thanks!

[DoctorKrolic]

@MartyIX I don't think we have a centralized place where all capabilities of semantic snippets are described. Maybe take a look at the original proposal, but it has quite a few outdated/not yet implemented details. But in short I can describe semantic snippets thre following way:

• They appear in completion list only where they are actually valid (e.g. you won't get class snippet inside a method)
• They try to avoid compiler errors when inserted (e.g. class snippet by default creates MyClass type, bu if there is already such name in the scope, snippet will generate MyClass1 to avoid naming conflict)
• They respect your code style settings (e.g. if you have 'Require accessibility modifiers' setting set to 'always' then class snippet will generate public class MyClass instead of just class MyClass)
• They have additional advanced features that aren't available for legacy snippets. For instance, we have what we reffer to as "inline statement snippets". These can be inserted if you type them after . as a member access, which is very useful (I myself use this thing a lot). An example here is:
  

[MartyIX]

That's a great description. Thank you!

[akhera99]

Looks good, thanks!

[DoctorKrolic]

@CyrusNajmabadi PTAL

[CyrusNajmabadi]

looks good. thanks!