Optional Exception on Mass-assignment of Protected Attributes

Oh, and by interest I mean more interest than just me and the company I work for.

+1

The ARes argument is the first one I've heard for not raising on an attempt to mass-update a protected attribute, and it seems like somewhat of an edge case. Given the developer headache that can arise from silently ignoring protected attrs (we have had tons), I'd be in favor of defaulting to raising and having a silent option.

+1

I think this should be configurable, so that the behavior can be different depending on environment.

This always bites me. I turn everything to protected by default and when using the console I try and use the short hand and I spend 5 minutes figuring our what I did wrong. Failing loudly would be preferable.

any input from core on this one?

+1

I'd love for raising to be the default, but getting the option would be a great start at least.

+1

The default is good, but I'd use this instead.

This was on by default for a while, but caused widespread low-level pain. I'm not sure that turning it on and off application-wide will really help with that.

+1 - I often overlook the debugging messages inadvertently.