by Tim Hunt.
Do we have a good deprecation process for web service functions?
If this was a Moodle internal API, we would
- Implement the new function / class / whatever API change.
- Modify the old functions so that using them causes a warning message.
- Announce in the release notes for that Moodle release that the old API is now deprecated.
- A few Moodle releases later, remove the old API.
- Announce in the release notes for that Moodle release that the old API is now gone.
That is a good system. Can we come up with an equivalent for web service APIs?
The only place I can think of to put the warning message is in the PHP logs on the Moodle server, and they are highly likely to not be seen. However, I hope there is a better option that I have failed to think of.