Skip to content

Move to newer xUnit packages #43598

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

Merged
merged 2 commits into from
Aug 28, 2022

Conversation

dougbu
Copy link
Member

@dougbu dougbu commented Aug 27, 2022

dougbu and others added 2 commits August 27, 2022 10:22
- move to `2.4.2` version of most xUnit packages
  - we were slightly behind Arcade SDK here and newer version has some fixes
  - _could_ reuse Arcade SDK's `$(XUnitVersion)`
    - that would require moving e.g. `$(XUnitAssertVersion)` to (say) CSharp.Common.props
    - VersionDefaults.props in SDK imports our Versions.props before setting its defaults
  - react to nullability errors due to new annotations in this version
- move to XUnit.Abstractions `1.0.0`
  - react to issues new analyzer finds
See xunit/xunit#2564
Workaround this issue by avoiding a cast between nullable numeric types.
@dougbu
Copy link
Member Author

dougbu commented Aug 27, 2022

Thanks for #43570 @ericstj.

All, this PR uses the latest xUnit packages and includes fixes for new problems the analyzer finds as well as a necessary workaround (look for a few more L literals) for the lack of an unintended xUnit feature in new version.

@dougbu dougbu merged commit 882c0d3 into dotnet:release/7.0 Aug 28, 2022
@dougbu dougbu deleted the dougbu/newer.xUnit.and.workarounds branch August 28, 2022 03:51
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.

3 participants