Hello @AdvanceLoanTechnologies!
I see the changelog entry you found mentioned that change within a same minor version update (1.3.0 changelog).
Seems this setting was completely removed as soon as version 2.0.0 was released (ExtJS 4.x) but, as a major update release, the breaking change was not even considered in the huge changelog it would make, or was just overlooked for the nature of big changes between major releases.
Anyway, by chance somebody had a similar inquiry from you in Sencha ExtJS forums' and, by chance, Daniil responded to him with the new expected approach,
CheckChangeBuffer. The Sencha thread is at
validationDelay is OBE - Sencha Forums.
Most breaking changes (if not all) you'll find are breaking changes that happen in-between major versions, not over major versions. That's why you don't see about the ValidateDelay setting being removed. We try to avoid them the best we can, but can't be helped when a feature is fully modified from Sencha.
Currently we are marking renamed/moved methods as [Obsolete] in C# so that we can remove them in next release and make the breaking change (remove instead of marking as obsolete) only when the change required for backwards compatibility is so big it may compromise the code stability. Unfortunately we can't control breaking changes published by Sencha, and all we can do is try whenever feasible to keep backwards-compatible references and track them so that we remove them completely on the next major release.
This new behavior though, will allow us now to track at least a number of removed/changed breaking changes. Can't say whether it will be feasible to track every breaking change in the next major ExtJS release, as it can change at will.
When I say major releases, I'm referring to version changes like from 1.7 to 2.0 and 3.3 to 4.0, and so on. Then the first number before the dot changes in our versions.
I hope the solution provided above works for you and that you understand about the difficulty on logging breaking changes between major version releases. But don't worry, if you have trouble finding alternatives to such changes, we're here to help!
