[eluser]OverZealous[/eluser]
@NachoF
It's actually a great find because I've come up with a better solution than previous.
I've replaced the generic
stdClass error object with a custom class. This class automatically returns the empty string for
any field, so this error could never happen. It also has better documentation, so code completion will work to show the common options (string, all, transaction), as well as hinting for the field names.
Another benefit is there is no need to set an empty string for every field anymore, (microscopically) reducing memory usage. This all fits really well with the purpose of the 1.7 update (which is performance and cleanup).
Thanks for finding it!