ASP.NET MVC Core中如何实现依赖其他字段的条件验证？

In ASP.NET MVC Core, when you need validation logic that depends on multiple properties (like your requirement where Score < 4 requires Comment and ReasonIds to be filled), the most straightforward approach is to have your model implement the IValidatableObject interface. This interface lets you write instance-level validation logic that can access all properties of the model, avoiding the limitations of data annotations that can't reference other fields as parameters.

Here's how to modify your Report class to add this validation:

using System.Collections.Generic;
using System.ComponentModel.DataAnnotations;

public class Report : IValidatableObject
{
    public int Score { get; set; }
    public string Comment { get; set; }
    public int[] ReasonIds { get; set; }

    public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
    {
        // Check if Score is below the threshold
        if (Score < 4)
        {
            // Validate Comment isn't empty or whitespace
            if (string.IsNullOrWhiteSpace(Comment))
            {
                yield return new ValidationResult(
                    "Comment is required when Score is less than 4.",
                    new[] { nameof(Comment) });
            }

            // Validate ReasonIds has at least one value
            if (ReasonIds == null || ReasonIds.Length == 0)
            {
                yield return new ValidationResult(
                    "ReasonIds must contain at least one value when Score is less than 4.",
                    new[] { nameof(ReasonIds) });
            }
        }
    }
}

How This Works: #

1. Interface Implementation: By implementing IValidatableObject, you define a Validate method that runs after any data annotation validations. This method has access to the entire model instance, so you can check dependent properties easily.
2. Conditional Checks: We first verify if Score is less than 4. If true, we then validate the required fields:
   • Comment can't be null, empty, or just whitespace.
   • ReasonIds can't be null and must have at least one element.
3. Error Association: Each validation failure returns a ValidationResult that links the error message to the specific property. This ensures errors show up next to the correct field in your view.

Using This in Your Controller: #

You can trigger the validation just like you would with standard data annotations:

[HttpPost]
public IActionResult SubmitReport(Report report)
{
    if (!ModelState.IsValid)
    {
        // Return the view with validation errors displayed to the user
        return View(report);
    }

    // Process the valid report submission
    return RedirectToAction("SubmissionSuccess");
}

Optional: Client-Side Validation #

Note that IValidatableObject validation runs only on the server. For immediate user feedback, you can add custom JavaScript to replicate the logic client-side:

// Add this script to your view (adjust selectors to match your form elements)
document.getElementById('Score').addEventListener('input', function() {
    const scoreValue = parseInt(this.value);
    const commentField = document.getElementById('Comment');
    const reasonIdsField = document.getElementById('ReasonIds');

    if (scoreValue < 4) {
        commentField.required = true;
        reasonIdsField.required = true;
    } else {
        commentField.required = false;
        reasonIdsField.required = false;
    }
});

Always keep in mind: client-side validation is for user convenience only—server-side validation is the single source of truth since client-side checks can be bypassed.

内容的提问来源于stack exchange，提问作者Mate Gvenetadze