Skip to content

Fix wording in CA2224 doc #49498

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.

Sign up for GitHub

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 1 commit into from
Oct 27, 2025
Merged

Fix wording in CA2224 doc #49498

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/fundamentals/code-analysis/quality-rules/ca2224.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "CA2224: Override equals on overloading operator equals"
description: "Learn about code analysis rule CA2224: Override equals on overloading operator equals"
title: "CA2224: Override Equals() on overloading operator equals"
description: "Learn about code analysis rule CA2224: Override Equals() on overloading operator equals"
ms.date: 11/04/2016
f1_keywords:
- "CA2224"
Expand All @@ -10,7 +10,7 @@ helpviewer_keywords:
- "OverrideEqualsOnOverloadingOperatorEquals"
- "CA2224"
---
# CA2224: Override Equals on overloading operator equals
# CA2224: Override Equals() on overloading operator equals

| Property | Value |
|-------------------------------------|------------------------------------------------|
Expand All @@ -22,7 +22,7 @@ helpviewer_keywords:

## Cause

A public type implements the equality operator but doesn't override <xref:System.Object.Equals%2A?displayProperty=fullName>.
A public type implements the equality operator but doesn't override the <xref:System.Object.Equals%2A?displayProperty=fullName> method.

## Rule description

Expand All @@ -33,11 +33,11 @@ The equality operator is intended to be a syntactically convenient way to access

## How to fix violations

To fix a violation of this rule, you should either remove the implementation of the equality operator, or override <xref:System.Object.Equals%2A> and have the two methods return the same values. If the equality operator does not introduce inconsistent behavior, you can fix the violation by providing an implementation of <xref:System.Object.Equals%2A> that calls the <xref:System.Object.Equals%2A> method in the base class.
To fix a violation of this rule, you should either remove the implementation of the equality operator, or override <xref:System.Object.Equals%2A> and have the two methods return the same values. If the equality operator doesn't introduce inconsistent behavior, you can fix the violation by providing an implementation of <xref:System.Object.Equals%2A> that calls the <xref:System.Object.Equals%2A> method in the base class.

## When to suppress warnings

It is safe to suppress a warning from this rule if the equality operator returns the same value as the inherited implementation of <xref:System.Object.Equals%2A>. The examples in this article include a type that could safely suppress a warning from this rule.
It's safe to suppress a warning from this rule if the equality operator returns the same value as the inherited implementation of <xref:System.Object.Equals%2A>. The examples in this article include a type that could safely suppress a warning from this rule.

## Suppress a warning

Expand Down
Loading