FLTFY15: MaybeNull is redundant for nullable properties
June 17, 2026 ยท View on GitHub
| Type Name | FLTFY15_NullabilityAttributeAnalyzer |
| CheckId | FLTFY15 |
| Category | Usage |
Cause
A nullable property on a type annotated with Fluentify is also annotated with MaybeNull.
Rule Description
Generated Fluentify extensions already allow null to be assigned to nullable properties. Applying MaybeNull to a nullable property is redundant for Fluentify null-assignment behavior.
How to Fix Violations
Remove the redundant MaybeNull attribute.
Example
using System.Diagnostics.CodeAnalysis;
using Fluentify;
[Fluentify]
public sealed class Actor
{
[MaybeNull]
public string? Name { get; init; }
}
Use the nullable annotation without MaybeNull.
using Fluentify;
[Fluentify]
public sealed class Actor
{
public string? Name { get; init; }
}
How to Suppress Violations
#pragma warning disable FLTFY15 // MaybeNull is redundant for nullable properties
How to Disable FLTFY15
dotnet_diagnostic.FLTFY15.severity = none