Remove obsolete external access API now that intellicode has switched over#61635
Merged
dibarbet merged 1 commit intodotnet:release/dev17.3from Jun 1, 2022
Merged
Conversation
CyrusNajmabadi
approved these changes
Jun 1, 2022
jasonmalinowski
approved these changes
Jun 1, 2022
Member
jasonmalinowski
left a comment
There was a problem hiding this comment.
Woohoo for actually deleting ExternalAPI stuff!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The old implementation could sometimes throw if there were no actual document changes (results[originalDocument.Id] would not be added to the dictionary in that case). We don't need to access it when they're using the new property, so just remove it.