Feature Request: Allow required Modifier on Entire record Type

[Manu-APO]

In C# 9.0, required modifiers were introduced for properties in a record type, making it easier to ensure properties are initialized during object creation. However, developers currently need to explicitly mark each property with the required keyword to enforce this behavior:

public record EmailSettingsModel
{
    public required string SenderEmail { get; init; }
    public required string Username { get; init; }
    public required string Password { get; init; }
    public required string Address { get; init; }
    public required int Port { get; init; }
}

While this works fine, it can become cumbersome when dealing with large record types that have many properties. It would be useful if C# allowed the required modifier to be applied to the entire record type, automatically marking all properties as required without the need to annotate each one individually.

Suggested Change

Allow the required modifier to be applied at the record level, so all properties in the record are implicitly considered required. This would eliminate the need to annotate each individual property with required.

For example, the following code would automatically apply the required modifier to all properties:

public required record EmailSettingsModel
{
    public string SenderEmail { get; init; }
    public string Username { get; init; }
    public string Password { get; init; }
    public string Address { get; init; }
    public int Port { get; init; }
}

In this example, all the properties would be required, meaning they must be initialized when the EmailSettingsModel is created, but we avoid the repetitive application of required to each property.

Benefits

• Simplifies code: For record types with many properties, this change would eliminate the need to repeatedly apply the required modifier, reducing boilerplate.
• Consistency: When using the required modifier across a record, it would be consistent across all properties without needing to track each individual one.
• Ease of Use: It would make the required modifier easier to apply in scenarios where all properties should be mandatory to initialize, streamlining the definition of configuration models, data transfer objects (DTOs), etc.

Example Scenario

Consider a large configuration model that has many properties that must be initialized during object creation:

public required record AppSettingsModel
{
    public string AppName { get; init; }
    public string Environment { get; init; }
    public string ConnectionString { get; init; }
    public int MaxRetries { get; init; }
    public bool EnableLogging { get; init; }
    // ... many more properties
}

In this case, marking record as required would ensure that all properties are required to be initialized, without needing to repeat required for each property individually.