-
Notifications
You must be signed in to change notification settings - Fork 291
Remove redudnant internals visible to in ms test.source generation #5438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove redudnant internals visible to in ms test.source generation #5438
Conversation
…ternalsVisibleTo-in-MSTest.SourceGeneration
…t.SourceGeneration
…t.SourceGeneration
…t.SourceGeneration
Evangelink
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not a super big fan of having public types when it's not needed - we have too many issues and problems linked to public types where we don't know if they are used preventing us from doing any change.
I also think IVTs kinda suck but from source to test it feels ok to me - at least preferable than public.
|
Keeping internal, and replacing by #5561 |
|
@Evangelink but isnt this a source generator package, and hence not possible for people to reference its types as a public api |
It's technically possible to reference the types. But it requires adding an explicit reference in csproj similar to: <Reference Include="$(NuGetPackageRoot)\package.name\package.version\analyzers\dotnet\cs\FileName.dll" />It's extremely uncommon though, and I personally wouldn't consider it as a supported scenario. Still, I would like to keep IVT for tests once the work for polyfill EmbeddedAttribute is done. I haven't yet got to complete my PR though, but hopefully soon I'll complete it. |
No description provided.