I do apologize for the migration difficulties that you had with the mentioned update.
We decided to make the change as in its previous state it imposed a vulnerability in the current API. Generally, it is not a recommended practice to have publicly settable collection properties as changing the original instance can lead to further problems.
The recommended approach while using the new implementation is to add the error instances to the collection exposed by the property. A sample project is attached for your reference. Can you please confirm whether the new logic can fully cover the scenario that you have on your side?
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items