Files
Terminal.Gui/Terminal.Gui.Analyzers/DiagnosticCategory.cs
Thomas Nind 3a645191db Fixes #4170 - Added analyzer that flags when user does not have Handled=true (#4182)
* Added analyzer

* WIP - Trying to create tests, failing with bad dependencies

* Working test woo

* Tidy up

* Tidy up

* Fix integration tests failing on command line

* Use 4.11 compiler

* Fix expecting 'e' as param name

* Make analyzer come as part of Terminal.Gui

* Add docs

* Fix warnings
2025-07-07 09:14:43 -06:00

68 lines
1.6 KiB
C#

namespace Terminal.Gui.Analyzers;
/// <summary>
/// Categories commonly used for diagnostic analyzers, inspired by FxCop and .NET analyzers conventions.
/// </summary>
internal enum DiagnosticCategory
{
/// <summary>
/// Issues related to naming conventions and identifiers.
/// </summary>
Naming,
/// <summary>
/// API design, class structure, inheritance, etc.
/// </summary>
Design,
/// <summary>
/// How code uses APIs or language features incorrectly or suboptimally.
/// </summary>
Usage,
/// <summary>
/// Patterns that cause poor runtime performance.
/// </summary>
Performance,
/// <summary>
/// Vulnerabilities or insecure coding patterns.
/// </summary>
Security,
/// <summary>
/// Code patterns that can cause bugs, crashes, or unpredictable behavior.
/// </summary>
Reliability,
/// <summary>
/// Code readability, complexity, or future-proofing concerns.
/// </summary>
Maintainability,
/// <summary>
/// Code patterns that may not work on all platforms or frameworks.
/// </summary>
Portability,
/// <summary>
/// Issues with culture, localization, or globalization support.
/// </summary>
Globalization,
/// <summary>
/// Problems when working with COM, P/Invoke, or other interop scenarios.
/// </summary>
Interoperability,
/// <summary>
/// Issues with missing or incorrect XML doc comments.
/// </summary>
Documentation,
/// <summary>
/// Purely stylistic issues not affecting semantics (e.g., whitespace, order).
/// </summary>
Style
}