Skip to content
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

Merged
merged 4 commits into from
Aug 12, 2024
Merged

Remove framework specific packages #1144

merged 4 commits into from
Aug 12, 2024

Conversation

sharwell
Copy link
Member

@sharwell sharwell commented Jan 31, 2024

@sharwell sharwell requested review from a team as code owners January 31, 2024 13:52
Comment on lines 49 to 57
* 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
Copy link
Member

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:

  1. People who have to migrate their packages forward won't have to change a bunch of package references/usings.
  2. 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.

Copy link
Member Author

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. 🎉

@sharwell

This comment was marked as outdated.

@sharwell
Copy link
Member Author

I updated this pull request to remove all framework specific packages.

@sharwell sharwell changed the title Remove xunit specific packages Remove framework specific packages Feb 21, 2024
@sharwell sharwell marked this pull request as ready for review February 21, 2024 15:52
@sharwell sharwell merged commit fd1b713 into dotnet:main Aug 12, 2024
9 checks passed
@sharwell sharwell deleted the no-xunit branch August 12, 2024 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

xUnit.net support broken with xUnit.net 2.5
3 participants