Eric Davis 7bca02b511 Instead of returning nil, which could get confused with No Rate, passing ...

incorrect objects to Rate#for will now throw a Rate::InvalidParameterException
back to the caller.

Normally you don't need to be this strict but this is a public API that will
be consumed by several third parties so we need to be very clear what happened.

  #1920

2009-01-16 16:53:00 -08:00

..

models

Instead of returning nil, which could get confused with No Rate, passing

2009-01-16 16:53:00 -08:00

views/users

Show a lock icon if a Rate is locked. #1915

2009-01-16 15:45:01 -08:00