Even though there is no conflict, name suggestion completions are numbered in some cases.
#73.291 aberto em 1 de mai. de 2024
Métricas do repositório
- Stars
- (20.414 stars)
- Métricas de merge de PR
- (Mesclagem média 6d 17h) (256 fundiu PRs em 30d)
Description
Version Used: 17.10.0 P6
Steps to Reproduce:
Unfortunately, I can't reproduce it in a pure console app, but the issue is present persistently in a mid-size project.
(The type in context is not partial, so there is no other identical method which may contain a parameter with the same name. It is not derived or implements an interface either.)
Diagnostic Id: N/A
Expected Behavior: Suggestions which have no naming conflict are not numbered.
Actual Behavior:
Even though there would be no naming conflict, some name suggestions are numbered: cancellationToken1.
- Other parameters don't produce this behavior (at least in this specific case), for example the parameter named
requestdoesn't get numbered suggestions, onlycancellationToken. - Suggestion
tokenis not numbered either. - If I remove the name of the parameter
cancellationToken, a reference remains in the body of the method. Even if I remove that reference, the issue remains present. - Recompilation doesn't resolve it.
These observations may make it more likely a bug in the suggestion logic, rather than the completion request served by a previous version of the semantic model (where that parameter existed - especially in the case if I simply overtype the old name and get suggestions offered)?