In this case, filtering serves a design purpose rather than a business
logic purpose.

I think it's fine here, since it's separating the design from the logic of
the view.
On Mar 15, 2013 12:50 PM, "Jeff Hemphill" <notifications@github.com> wrote:

> In HVZ/HVZ/main/templatetags/player_extras.py:
>
> >  @register.filter
> >  def upgrade_name(upgrade):
> >      if not upgrade:
> >          return ""
> > -    return Player.UPGRADES[upgrade]
> > +    return Player.UPGRADES.get(upgrade, '')
> > +
> > +
> > +@register.filter
> > +def filter_by(qs, keyvalue):
>
> I'm not sure why it's advantageous to play with querysets in the template
> instead of the view, especially since I don't understand/trust template
> caching very well/much.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Claremont-HvZ-Web-Team/claremontHvZ/pull/146/files#r3398167>
> .
>