[Rails-core] Re: attr_accessible on some properties + attr_protected on others makes class 'open-by-default'

2012-07-10 Thread Jay Feldblum
In this type of case, it makes sense either to declare a whitelist or to declare a blacklist. But it doesn't make much sense to declare both of them. Solution #3: ActiveRecord (or ActiveModel) should raise if a class declares both a whitelist and a blacklist of mass-assignable attributes. class

Re: [Rails-core] Re: attr_accessible on some properties + attr_protected on others makes class 'open-by-default'

2012-07-10 Thread Rafael Mendonça França
Jay, this solution doesn't play nice with inheritance. Rafael Mendonça França http://twitter.com/rafaelfranca https://github.com/rafaelfranca On Tue, Jul 10, 2012 at 10:59 AM, Jay Feldblum wrote: > In this type of case, it makes sense either to declare a whitelist or to > declare a blacklist.