- Notifications
You must be signed in to change notification settings - Fork311
Merge | Move ReliabilitySection / BestEffortCleanup to framework specific files#2984
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecovbot commentedNov 7, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@## main #2984 +/- ##==========================================+ Coverage 72.64% 72.67% +0.02%========================================== Files 285 286 +1 Lines 59160 59160 ==========================================+ Hits 42979 42995 +16+ Misses 16181 16165 -16
Flags with carried forward coverage won't be shown.Click here to find out more. ☔ View full report in Codecov by Sentry. |
c634c01
toac8aa33
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Overall I think this makes sense and is probably a good idea. Still not a huge fan of the conditional attribute, but since it's already there, I won't raise a fuss :)
@MichelZ if you can resolve the conflict, I can get this merged 🚢 |
@benrr101 Done! Thx |
5519887
intodotnet:mainUh oh!
There was an error while loading.Please reload this page.
I don't think we want to wrap those in #IF NETFRAMEWORK / NETCORE conditional compiles, it makes sense to have them in their own files, so I've moved them out of the "future-common-project" file(s)
Part of#2953