This is more of a request than a problem, but could the CakePHP core developer please cut down on the number of deprecations they introduce?
Right now I am converting an old CakePHP 1.3 based website to CakePHP 3, and inside the 3.x cookbook quite a few functions are already deprecated; most are only trivial renames like Email->subject() to Email->setSubject(). I’m a bit surprised that this happens even within a major release cycle; secondly, it would be nice if the examples are also immediately updated.
But today I checked out the AuthComponent document, and lo and behold I read:
and I’m like: “WTF? I just implemented the new authentication mechanism. Does it ever stop?!”
As for a rationale: this website is for a customer; he grudgingly approved the update because of the imminent phasing out of PHP 5.6. So this is costing the customer money, which is a-okay for the PHP reason but I can hardly justify charging him for changes just because the Cake core developers think it’s “better”.
With Cake I’m feeling that I am on a constant “deprecation treadmill”; just when you think you have a stable set you have to go back in and re-do your work. I wonder if others feel the same.