Thanks for your explanation.But I still want to mention that for us control users, the behavior changes of some basic interfaces may have a much greater impact than imagined.
In the process of product development to release, we will go through many testing stages. So the final version is stable, although some of its code may have errors, such as getting the current position word offset as plural, but they pass the test in this specific version.
After upgrading the control version, you may fix these problems before. There is no logical error, but the behavior of the interface has changed. So some problems with our previous release phase testing will be exposed.
I don't mean that it is wrong to do this, but that there will be a large number of calls to this type of basic interface, and we may not be able to upgrade it in the short term. And possibly a full test. But some bug fixes in the new version are problems we have to solve. Therefore, our expectation is that for changes in the behavior of this type of basic interface (including the previous wrong behavior is now correct), we should adopt a smoother adjustment, keep the old interface, mark it as expired, and provide a suggested new interface , let users decide when to upgrade and test it. Will this be better? Of course, this is just my personal suggestion, and more needs to be heard from you.