Filter out duplicate visualizers from evaluation result #81730
+124
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some expressions were returning with multiple instances of the IEnumerable Visualizer when using the Debug Adapter Protocol because it did not have the logic found in the Core Visual Studio debugger to filter them out. Instead of fixing it in that layer, I decided it best to address it when constructing the evaluation result since it is never necessary to have an evaluation result with multiple copies of the same visualizer.
Added test and verified that without the proposed changes it would fail because of multiple visualizers present in the result.