Intellisense suggestions are sometimes counterproductive

[karlra]

Since installing MappingGenerator my IntelliSense has started behaving a bit weird.

For example, if I try to create an instance of an interface and sometimes a class the IntelliSense will suggest some kind of equality check instead, like this (bottom one):

It only happens sometimes, haven't been able to find the exact situation yet.

The annoying thing is that the new suggestion is the default, so if you write a few characters and then tab-tab to autocomplete it will insert this equality check instead of the variable name that intellisense suggests normally. It's pretty annoying because it changes the muscle memory that is the VS default.

Would it be possible to at least be able to disable these intellisense suggestions that are not mapping related?

[cezarypiatek]

I will take a lookt at that. This definitely shouldn't be suggested in this case.

[cezarypiatek]

Please update to v2023.1.52. I made some improvements in this area. Let me know if the issue disappeared.

[karlra]

Still get the same result unfortunately. Weirdly it only happens sometimes.

[karlra]

There are some really other weird behaviours with intellisense introduced with this extension:

Would it be possible to have a setting to just disable every intellisense suggestion that is not related to pure mapping of DTOs? It bears mentioning that these weird suggestions are always the default too so it messes with the workflow quite a bit, and they're always really unexpected.

[cezarypiatek]

Thanks for providing those examples. I will try to verify why they appear in that form and provide an option to toggle code suggestion availability. Sorry for your inconvenience.

[cezarypiatek]

Since v2023.2.54 you can disable code suggestion by editing c:\Users\%USERNAME%\AppData\Roaming\MappingGenerator\Suggestions.json file which has the following content

{
  "MethodParametersSuggestions": false,
  "NotNullDereferenceSuggestions": false
}