Join GitHub today
AM::MassAssingmentSecurity: improve performance #5431
According to this article:
Current implementation of mass assignment security takes a lot of processor time because spawning to many redundant objects in
We can get rid of this method.
A little side effect of this patch attributes are processed one by one. Instead of:
The only one place where this could cause side effect is when someone wants to create it's own sanitizer(other than built-in Strict and Logger).
We can make a backward compatibility for this but decided that it doesn't make that much sense.