Change Details

In most cases, and even at the moment, MobileFrontend requires the latest MW version (now master requires 1.33), it would be also good practice to avoid uses of deprecated methods, classes or configs from core in the extension. I'm particularly interested in cleaning up deprecation usages and wooyaa my root extension for this will now be MobileFrontend. @pmiazga, @Jdlrobson, is it a good idea to always reduce usage of deprecated functions in this extension?

In most cases, and even at the moment, MobileFrontend requires the latest MW version (now master requires 1.33), it would be also good practice to avoid uses of deprecated methods, classes or configs from core in the extension. I'm particularly interested in cleaning up deprecation usages and wooyaa my root extension for this will now be MobileFrontend. @pmiazga, @Jdlrobson, is it a good idea to always reduce usage of deprecated functions in this extension? ===== Done so far [X] `Revision::*` constants [X] `getMFConfig()` method [ ] `Revision::*()` methods -- WIP

In most cases, and even at the moment, MobileFrontend requires the latest MW version (now master requires 1.33), it would be also good practice to avoid uses of deprecated methods, classes or configs from core in the extension. I'm particularly interested in cleaning up deprecation usages and wooyaa my root extension for this will now be MobileFrontend. @pmiazga, @Jdlrobson, is it a good idea to always reduce usage of deprecated functions in this extension? ===== Done so far [X] `Revision::*` constants [X] `getMFConfig()` method [ ] `Revision::*()` methods -- WIP