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
To Reproduce
Steps to reproduce the behavior:
Try to trigger suggestions for any widget you will see that every options displayed twice. I guess it happened when Dart Code extension was updated to 3.26.0
Expected behavior
Should seee only one option
Screenshots
Versions (please complete the following information):
Hi @DanTup it occurred because I added dart-code-metrics to my project, but first thought was that something wrong with the dart extension. I created the issue on dart-code-metrics you can review it
Since registration 3 was not removed, we end up with two Dart registrations, which results in VS Code asking for completions twice and the lists (which are identical) merged.
Activity
theSharpestTool commentedon Sep 10, 2021
Was caused by analysis_options.yaml
DanTup commentedon Sep 13, 2021
@theSharpestTool can you be more specific? I'd be interested to know what caused this to see if it could be handled better. Thanks!
theSharpestTool commentedon Sep 13, 2021
Hi @DanTup it occurred because I added
dart-code-metricsto my project, but first thought was that something wrong with the dart extension. I created the issue on dart-code-metrics you can review itDanTup commentedon Sep 13, 2021
Thanks - I can repro and this looks like a bug in the LSP initialisation, I'm taking a look.
DanTup commentedon Sep 13, 2021
This looks like an issue in the LSP initialisation when there are plugins. We register two completion providers:
Then when the plugin registers and we need to replace them, we only unregister one of them:
Then we re-register:
Since registration 3 was not removed, we end up with two Dart registrations, which results in VS Code asking for completions twice and the lists (which are identical) merged.
[analysis_server] Prevent duplicate LSP completion registrations for …
DanTup commentedon Sep 15, 2021
This is fixed in the SDK by dart-lang/sdk@f951279 and will show up in a future SDK release.