The whole point of MVC, or any other programming paradigm, is to get good separation of concerns. Slavish adherence to your paradigm's principles should be insisted upon only when you can specify a greater benefit to doing so than not.
If you're willing to accept the need to possibly edit your
View when a new headline rule comes along, skipping an empty property on the
PropertyController is probably fine. Especially if your
View already has an included dependency to the model.
On the other hand, if your
View has no other direct reference to the model, you'd probably be better off just defining the "empty" parameter on the
PropertyController, so you can change or move the logic without having to worry about the
(If you have a lot of these, you may want to explore a generic get function on the controller, and have the view call that instead of direct property or method references.)