Looking for suggestions on best way to find possible errors created when updating packages

[schakravarty]

So I just upgraded all of my kendo packages and there were multiple hidden problems after updating. I know that there is documentation on each component and change log, but I use most of the components offered and to go through every change log to find what may have broken my code would be very tedious. Is there not a way for the kendo team to do some upgrade fixes much like angular does when there is a code change that will break, they try to upgrade your code for you. In this last update it broke many areas of my application and I am still finding problems. Not a good experience...

[Martin Bechev]

Hi Paul,

Updating the kendo packages and used kendo theme to their latest stable versions is always recommended approach.

In the last major release, we have to introduce some breaking changes which confront our customers to invest time updating the codebase manually in order to fix the experiencing errors. But currently, there is no built-in mechanism that scans the code and does the required changes automatically. 

We understand that this could be a tedious and frustrating job sometimes, but there are updates that are unavoidable in the process of making the Kendo suite a better tool.

Please accept our apologies for the caused inconvenience and let us know in case any further questions come up regarding the built-in API of the suite.

Regards,
Martin
Progress Telerik