Change Details

Discussed: * MobileView api * Split it out to it's own extension * Improve test coverage, business use cases * Evaluate if refactoring would make sense * Improve RL usage in MobileFrontend * Either use a linter that matches dependency trees with the actual code * Or use an external bundler for the dependency graphs and just include entry points in extension.json * Extract Special:Nearby into its own extension Created: * T140882 Extracting MobileFormatter to a composer library * T138071 Fast isolated unit testing in MobileFrontend * T141087 Feature management ("flagging") * T141936 Progressively enhanced watchstar * T144402 Extract core/foundational UI components from MobileFrontend

==Created: * T140882 Extracting MobileFormatter to a composer library * T138071 Fast isolated unit testing in MobileFrontend * T141087 Feature management ("flagging") * T141936 Progressively enhanced watchstar * T144402 Extract core/foundational UI components from MobileFrontend ==Some day * MobileView api * Split it out to it's own extension * Improve test coverage, business use cases * Evaluate if refactoring would make sense * Extract Special:Nearby into its own extension ==Need more thought/discussion before tasking out * Improve RL usage in MobileFrontend * Either use a linter that matches dependency trees with the actual code * Or use an external bundler for the dependency graphs and just include entry points in extension.json

Discussed:==Created: * T140882 Extracting MobileFormatter to a composer library * T138071 Fast isolated unit testing in MobileFrontend * T141087 Feature management ("flagging") * T141936 Progressively enhanced watchstar * T144402 Extract core/foundational UI components from MobileFrontend ==Some day * MobileView api * Split it out to it's own extension * Improve test coverage, business use cases * Evaluate if refactoring would make sense * Extract Special:Nearby into its own extension ==Need more thought/discussion before tasking out * Improve RL usage in MobileFrontend * Either use a linter that matches dependency trees with the actual code * Or use an external bundler for the dependency graphs and just include entry points in extension.json * Extract Special:Nearby into its own extension Created: * T140882 Extracting MobileFormatter to a composer library * T138071 Fast isolated unit testing in MobileFrontend * T141087 Feature management ("flagging") * T141936 Progressively enhanced watchstar * T144402 Extract core/foundational UI components from MobileFrontend