-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unnecessary ApiCompat CP0001 errors when type forwards used #31271
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsSee dotnet/runtime#82453 (comment) for more detail. Local errors for when the https://github.com/dotnet/runtime/tree/main/src/libraries/System.DirectoryServices/src/CompatibilitySuppressions.xml file is removed (please delete that file when this issue is fixed):
|
This happens because on the baseline comparison APICompat doesn't resolve any references. sdk/src/ApiCompat/Microsoft.DotNet.ApiCompatibility/Runner/ApiCompatRunner.cs Lines 118 to 121 in 2fd62c3
This is done today because we don't go and restore the baseline package for all of it's frameworks to get those references (including ones from targeting pack, etc). While that might be "most correct" I don't think it's work that's worth the effort. The way I previously discussed making this work was using the right-hand-side references for the left-hand-side baseline so long as we have them. This should work since those references need to be transitively compatible with the left-hand-side and we're not interested in validating compatibility of left-hand-side assemblies that are only part of the references and not assemblies under test. |
@dotnet/area-infrastructure-libraries a new issue has been filed in the ApiCompat area, please triage |
Closed by #32930 |
See dotnet/runtime#82453 (comment) for more detail.
Local errors for when the https://github.com/dotnet/runtime/tree/main/src/libraries/System.DirectoryServices/src/CompatibilitySuppressions.xml file is removed (please delete that file when this issue is fixed):
The text was updated successfully, but these errors were encountered: