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

Fix UTs caused by .NET 8 release by using specific nuget version #8362

Merged
merged 1 commit into from
Nov 15, 2023

Conversation

sebastien-marichal
Copy link
Contributor

No description provided.

Copy link
Contributor

@antonioaversa antonioaversa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sebastien-marichal sebastien-marichal changed the title Fix UTs by fixing nuget version Fix UTs caused by .NET 8 release by using specific nuget version Nov 15, 2023
Copy link

sonarcloud bot commented Nov 15, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@@ -64,7 +64,7 @@ public class UriShouldNotBeHardcodedTest

[DataTestMethod]
[DataRow("2.0.4", "2.0.3", "2.1.1")]
[DataRow(Constants.NuGetLatestVersion, Constants.NuGetLatestVersion, Constants.NuGetLatestVersion)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will you open a ticket to bring this back to NuGet Latest?

why: we keep LatestVersion to be aware if some API changes lead to our rules creating FPs or FNs (e.g. a deprecated attribute might be removed, so we won't raise anymore on net8 and we need to update the rule)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I created the ticket #8363

The goal would be to revert this PR when changing the target framework of the UT project to net8.0

@@ -150,7 +150,7 @@ public class SkipMigration : Migration

protected override void Up(MigrationBuilder migrationBuilder) { }
}
}").AddReferences(EntityFrameworkCoreReferences(Constants.NuGetLatestVersion)).Verify();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will you open a ticket to bring this back to NuGet Latest?

For example, will we still ignore migrations on Net 8?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No we will revert this PR during the migration of UT project to net8.0

@@ -76,7 +76,7 @@ public class PermissiveCorsTest
.Verify();

private static IEnumerable<MetadataReference> AdditionalReferences =>
NuGetMetadataReference.MicrosoftNetHttpHeaders(Constants.NuGetLatestVersion)
NuGetMetadataReference.MicrosoftNetHttpHeaders("2.1.14")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will you open a ticket to bring this back to NuGet Latest?

why: we keep LatestVersion to be aware if some API changes lead to our rules creating FPs or FNs (e.g. a deprecated attribute might be removed, so we won't raise anymore on net8 and we need to update the rule)

Copy link

sonarcloud bot commented Nov 15, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@sebastien-marichal sebastien-marichal merged commit b69d763 into master Nov 15, 2023
38 checks passed
@sebastien-marichal sebastien-marichal deleted the sebastien/ut-net8-fix branch November 15, 2023 11:30
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