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

Bump Xunit to V3 to resolve transitive ambiguity problems #58

Open
Ducki opened this issue Feb 7, 2025 · 2 comments
Open

Bump Xunit to V3 to resolve transitive ambiguity problems #58

Ducki opened this issue Feb 7, 2025 · 2 comments
Assignees

Comments

@Ducki
Copy link

Ducki commented Feb 7, 2025

If the testing project is using Xunit 3, references to the Assert method and others fail because this library references Xunit 2. The compiler then has ambiguity problems that cannot seem to be resolved by using aliases.

It would be nice, if there was a version of this library, that uses Xunit 3 as well.

@lateapexearlyspeed lateapexearlyspeed self-assigned this Feb 8, 2025
@lateapexearlyspeed
Copy link
Owner

Hi @Ducki thanks for issue.

I checked and seems because xunit v3 uses assertion pack whose name is new xunit.v3.assert. Based on its practice guidance, I also create new separate lib with new name as what xunit.net did, for xunit v3.

For your xunit v3 test project, please use LateApexEarlySpeed.Xunit.V3.Assertion.Json which references xunit.v3.assert, thanks.

(Will also update doc for supporting xunit v3 project)

@Ducki
Copy link
Author

Ducki commented Feb 8, 2025

Thank you so much! <3

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

No branches or pull requests

2 participants