-
Notifications
You must be signed in to change notification settings - Fork 256
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 framework specific packages #1144
Conversation
* Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit | ||
* Microsoft.CodeAnalysis.CSharp.CodeFix.Testing.XUnit | ||
* Microsoft.CodeAnalysis.CSharp.CodeRefactoring.Testing.XUnit | ||
* Microsoft.CodeAnalysis.CSharp.SourceGenerators.Testing.XUnit | ||
* Microsoft.CodeAnalysis.CSharp.Analyzer.Testing | ||
* Microsoft.CodeAnalysis.CSharp.CodeFix.Testing | ||
* Microsoft.CodeAnalysis.CSharp.CodeRefactoring.Testing | ||
* Microsoft.CodeAnalysis.CSharp.SourceGenerators.Testing | ||
* Visual Basic | ||
* Microsoft.CodeAnalysis.VisualBasic.Analyzer.Testing.XUnit | ||
* Microsoft.CodeAnalysis.VisualBasic.CodeFix.Testing.XUnit | ||
* Microsoft.CodeAnalysis.VisualBasic.CodeRefactoring.Testing.XUnit | ||
* Microsoft.CodeAnalysis.VisualBasic.SourceGenerators.Testing.XUnit | ||
* Microsoft.CodeAnalysis.VisualBasic.Analyzer.Testing | ||
* Microsoft.CodeAnalysis.VisualBasic.CodeFix.Testing | ||
* Microsoft.CodeAnalysis.VisualBasic.CodeRefactoring.Testing | ||
* Microsoft.CodeAnalysis.VisualBasic.SourceGenerators.Testing |
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.
This very much worries me here that we're making a source breaking change more or less for folks who consumed this. It seems a much smaller change would just be to remove the verifier implementation that is causing trouble here, and leave the packages and core scaffolding in place. This way:
- People who have to migrate their packages forward won't have to change a bunch of package references/usings.
- If we still have xunit specific value we do want to provide (say, xunit does offer a way to have richer exceptions), we have a natural process for restoring that without asking everybody to change their package references/usings again.
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.
We published a public 1.2 release with these types marked obsolete, finally giving us a path forward to remove them. 🎉
This comment was marked as outdated.
This comment was marked as outdated.
I updated this pull request to remove all framework specific packages. |
See #1099 (comment)
See #1127 (comment)
Closes #1099