-
Task
-
Resolution: Done
-
Medium
-
None
For the initial deprecation of a class:
- Add @deprecated tag on class level PHPDoc block
- Add @deprecated tag on the PHPDoc block of all public methods
- Add debugging on all of the public methods
And for the final deprecation of a class, it must be completely removed.
The Deprecation policy (https://docs.moodle.org/dev/Deprecation#Step_1._Immediate_action) is very outdated and it does not state what to do with a class which has been finally deprecated.
The options are really:
- remove them
- make them throw an exception but keep them around
- something else I haven't thought of
I'd prefer the first option of removing them, but we should probably stay in keeping with the global function section of the Deprecation policy which states that a function should throw an Exception.
- blocks
-
MDL-64866 Remove message/defaultoutputs.php and final deprecation of admin_page_manageqbehaviours class
- Closed
-
MDL-69655 Final deprecation of admin_setting_managelicenses
- Closed
-
MDL-61165 Remove support for Legacy cron
- Closed
- has been marked as being related by
-
MDL-66239 Document various deprecation processes
- Open