Refaktorisierung des Flag-Enums: Flag auf nullable gesetzt, HasFlag-Methode für Nullable-Prüfung aktualisiert, Null-Flag entfernt, SecurityBreachOrDataIntegrity für überlappende Probleme hinzugefügt.
This commit is contained in:
@@ -14,6 +14,19 @@
|
||||
/// <summary>
|
||||
/// Indicates a security breach or vulnerability has been detected during the service operation.
|
||||
/// </summary>
|
||||
SecurityBreach
|
||||
SecurityBreach,
|
||||
|
||||
/// <summary>
|
||||
/// Indicates a potential issue with data integrity during the service operation.
|
||||
/// This flag is used when data may have been altered, corrupted, or is otherwise unreliable,
|
||||
/// which could impact the accuracy or trustworthiness of the operation's results.
|
||||
/// </summary>
|
||||
DataIntegrityIssue,
|
||||
|
||||
/// <summary>
|
||||
/// Indicates that either a security breach, a data integrity issue, or both have been detected during the service operation.
|
||||
/// This flag is used when one or both types of issues are present, requiring heightened attention to both security and data accuracy.
|
||||
/// </summary>
|
||||
SecurityBreachOrDataIntegrity
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user