Hi Brady, I agree that E_WARNING is a poor way to handle this limit, and IMO a fatal error should be triggered instead. The ability to suppress and ignore is the root cause of why your situation is possible at all, and Laravel's behavior in this instance also did you a massive disservice.
That being said however, this is also an extreme and self-inflicted edge case. 1k is an absurd number, even 100 input vars should be a sign of poor code logic. I urge you to redesign your solution entirely instead of looking for a quick workaround. Cheers, Andrey.
