refactor: update to .NET SDK version 10.0.300#781
Conversation
There was a problem hiding this comment.
Pull request overview
Bumps the .NET SDK pin from 10.0.201 to 10.0.300 and refreshes the public-API baseline snapshots (Mockolate_netstandard2.0.txt, Mockolate_net8.0.txt, Mockolate_net10.0.txt) to match the new SDK's API-extractor rendering of extension declarations. The previous output emitted extension<T>(... <T> setup) where T : notnull; the new SDK renders the same declarations as extension<T>(... <T?>? setup) (constraint removed, generic args and parameter annotated nullable). No source code is changed — only the SDK version and the expected-output text files used by the API compatibility tests.
Changes:
- Update
global.jsonSDK to10.0.300. - Regenerate API baseline files for netstandard2.0, net8.0, and net10.0 to match the new compiler/API-extractor formatting of
extensionblocks.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| global.json | Bumps SDK version to 10.0.300. |
| Tests/Mockolate.Api.Tests/Expected/Mockolate_netstandard2.0.txt | Refreshes extension declarations to new nullable-annotated rendering. |
| Tests/Mockolate.Api.Tests/Expected/Mockolate_net8.0.txt | Same baseline refresh for net8.0. |
| Tests/Mockolate.Api.Tests/Expected/Mockolate_net10.0.txt | Same baseline refresh for net10.0. |
|
🚀 Benchmark ResultsDetails
Details
Details
Details
Details
Details
|
….0.300 (#781) by Valentin Breuß
….0.300 (#781) by Valentin Breuß



This pull request updates the extension method signatures in
Mockolateto improve nullability handling and simplify type constraints. The changes make the extension methods more flexible by allowing nullable types and optional builder parameters, and by removing unnecessarynotnullconstraints.Nullability and Type Constraint Updates
Mockolate.SetupandMockolate.Verifynow accept nullable generic type arguments (e.g.,T?,T1?, etc.) and the builder parameters themselves are now nullable (e.g.,IPropertySetupReturnWhenBuilder<T?>?). This change increases the flexibility of the API and improves compatibility with nullable reference types.where T : notnulland similar type constraints have been removed from all relevant extension methods, further relaxing the requirements on generic parameters.