Skip to content

CSHARP-5512: Convert LINQ-related tests to use fixtures #1710

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 3 commits into from
Jun 30, 2025

Conversation

sanych-sun
Copy link
Member

Another batch of LINQ-related tests converted to use Fixtures.

@sanych-sun sanych-sun requested a review from rstam June 13, 2025 22:48
@sanych-sun sanych-sun requested a review from a team as a code owner June 13, 2025 22:48
@sanych-sun sanych-sun added the chore Label to hide PR from generated Release Notes label Jun 13, 2025
@sanych-sun sanych-sun changed the title CSHARP-5512: Convert LINQ-related tests to use fixtures. CSHARP-5512: Convert LINQ-related tests to use fixtures Jun 13, 2025
Copy link

Assigned mongoKart for team dbx-csharp-dotnet because rstam is out of office.

@sanych-sun sanych-sun removed request for a team and mongoKart June 24, 2025 15:52
Copy link
Contributor

@rstam rstam left a comment

Choose a reason for hiding this comment

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

One small question before I LGTM.

@@ -15,6 +15,7 @@
<NoWarn>
1701;1702; <!--https://github.com/dotnet/roslyn/issues/19640-->
CA1724; <!--The type name Model conflicts in whole or in part with the namespace name. Change either name to eliminate the conflict. (https://docs.microsoft.com/visualstudio/code-quality/ca1724-type-names-should-not-match-namespaces)-->
CA1714; <!-- Flags enums should have plural names -->
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you sure you want to disable this warning project-wide?

Copy link
Member Author

@sanych-sun sanych-sun Jun 27, 2025

Choose a reason for hiding this comment

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

We have to either suppress the warning or rename enums as recommended. I do remember we had similar problem with class named "Model" and we decided to suppress the warning instead of renaming (see line above the commented). But I'm OK with renaming if in this case we do not want to suppress the warning.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm fine with suppressing the warnings, but I think it should be done on a case by case basis instead of project wide.

Are there a lot of these? What motivated you to do it project wide instead of an a case by case basis?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll check.

Copy link
Member Author

Choose a reason for hiding this comment

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

Found 1 problem so far, suppressed with #pragma

@@ -15,6 +15,7 @@
<NoWarn>
1701;1702; <!--https://github.com/dotnet/roslyn/issues/19640-->
CA1724; <!--The type name Model conflicts in whole or in part with the namespace name. Change either name to eliminate the conflict. (https://docs.microsoft.com/visualstudio/code-quality/ca1724-type-names-should-not-match-namespaces)-->
CA1714; <!-- Flags enums should have plural names -->
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm fine with suppressing the warnings, but I think it should be done on a case by case basis instead of project wide.

Are there a lot of these? What motivated you to do it project wide instead of an a case by case basis?

@sanych-sun sanych-sun requested a review from rstam June 30, 2025 20:11
Copy link
Contributor

@rstam rstam left a comment

Choose a reason for hiding this comment

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

LGTM

@sanych-sun sanych-sun merged commit 99ff1ed into mongodb:main Jun 30, 2025
31 of 35 checks passed
@sanych-sun sanych-sun deleted the csharp5512 branch June 30, 2025 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Label to hide PR from generated Release Notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants