Question

I understand that a view should only display stuff and do no logic itself outside of what is required to display information.

What is the best way, in keeping that in mind, to handle this kind of simple scenario:

1. User clicks Delete Item
2. If the item is still associated with others, show “you can’t delete this.”
3. Else, show a confirm form that posts to action /Delete/Id

I could very easily in the view do something like:

@if (Model.Children.Count > 0)
{
  <p>
    You can't delete this!
  </p>
}
else
{
  using (Html.BeginForm())
  {
    <p>
        Are you really sure you want to delete this?
    </p>
    <p>
        <input type="submit" value="Confirm" /> |
        @Html.ActionLink("Cancel", "Index")
    </p>
  }
}

Is there a compelling reason to make TWO Views and have the controller return the appropriate view depending on how many children there are? Seems like a tradeoff of simplicity and separation of concerns.

Answer 1

It’s a pretty simple example, so at first glance it appears harmless (and if it stays that way it certainly is). However, keep these factors in mind:

• What if it becomes more than just children? Maybe three other relationships appear over time, and now you need to check for all of them in your view? Suddenly the code smell is a lot stronger.
• Putting this type of logic in the controller may make other approaches to the problem more obvious or easy later, e.g., adding an ajax version that lets you give the user the “you can’t delete this” feedback without leaving the previous page.