Skip to content

Add support for custom unnecessary locations on a diagnostic.#39649

Merged
dibarbet merged 6 commits intodotnet:masterfrom
dibarbet:dupe_error_list
Jan 2, 2020
Merged

Add support for custom unnecessary locations on a diagnostic.#39649
dibarbet merged 6 commits intodotnet:masterfrom
dibarbet:dupe_error_list

Conversation

@dibarbet
Copy link
Member

@dibarbet dibarbet commented Nov 2, 2019

No description provided.

@dibarbet dibarbet added this to the 16.5.P1 milestone Nov 2, 2019
@dibarbet dibarbet requested review from a team and mavasani November 2, 2019 02:28
@CyrusNajmabadi
Copy link
Contributor

LMK when you'd like a review. thanks!

@dibarbet
Copy link
Member Author

dibarbet commented Nov 4, 2019

LMK when you'd like a review. thanks!

I think you should be able to take a look. Was thinking about just encoding the locations into the property bag, but I think this ends up being easier since I get the conversion to DiagnosticDataLocation for relatively free. Just looking into the newtonsoft json version issues now.

@dibarbet dibarbet marked this pull request as ready for review November 5, 2019 18:53
@dibarbet dibarbet requested a review from srivatsn as a code owner November 5, 2019 18:53
Copy link
Contributor

@mavasani mavasani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM. Just have some suggestions around adding more defensive code and adding an example to doc comments. Lets hope we can use the API you added to get rid of the remaining fake fading diagnostics in follow-up PR(s).

@jinujoseph jinujoseph modified the milestones: 16.5.P1, 16.5 Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants