I’m a bit confused. The so called ”Legacy libraries” have all sorts of handy classes that I would like to use. The Input class for example.
But what does ”legacy” really mean here? I get that they are the are a legacy from the previous versions of EE, but does that mean that development will stop and that they will be removed in the near future?
And the big question is: should I even use them in my own addons or will I be left in the dust with a fossil application that is a dead dinosaur when the libraries are removed down the road?
Regards, Matts
Good question- I’d use them if there’s isn’t a newer alternative that does the same thing. Do not use deprecated- and you’ll know they’re deprecated because those will show up in the developer logs.
But legacy is fine and used natively and as things are updated they’ll move over to services etc. with plenty of warning and deprecation notices and an easy update path if needed. Or none needed at all. But nothing will go poof without a ton of explicit warning and an upgrade path. And the core depends heavily on methods in legacy, so you’ll be in good company.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.