APIView - Visualize when assemblies expose internals via InternalsVisibleTo #7116
Conversation
This file contains 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
christothes
requested review from
JoshLove-msft and
KrzysztofCwalina
and removed request for
chidozieononiwu
praveenkuttappan
approved these changes
Oct 26, 2023
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.
This change allows APIView to display when a client library exposes its internals to other assemblies (excluding Moq,
.Tests, and.Perf) as well as any types that are designated as exposed via decoration with aFriendAttribute.The following is what a diff looks like for
Azure.Identity, which exposes internals toAzure.Identity.BrokeredAuthenticationThe following shows that the internals consumers can be commented:
related #7086