Avoid redundant modifiers

Documentos > Code Analysis > Static Analysis Rules > Avoid redundant modifiers

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

ID: csharp-best-practices/redundant-modifiers

Language: C#

Severity: Notice

Category: Best Practices

Description

When sealed is used in the class definition, methods and attributes do not need to define or use the sealed modifier.

Non-Compliant Code Examples

public sealed class MyClass {

    public sealed void myMethod() {
        
    }
    sealed void myMethod() {
        
    }
}

Compliant Code Examples

class MyClass {
    public sealed myMethod()
    {
        if (foo) {
            throw new MyException();
        }
        
    }
}

How to use this rule

1
2
rulesets:
  - csharp-best-practices     # Rules to enforce C# best practices.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products