Change Details

= Documentation on wiki https://m.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture#Review_and_refactor_components = WIP audit of existing MobileFrontend components https://docs.google.com/document/d/1pxTYAu6tIIPR-8TpUJ5_qKdumj8P76k3cbVo-WJAuzU/edit?usp=sharing = What When the previous projects have been successful (see parent task and task graph), we will generate a concrete proposal for this epic. Some goals for this would be: * Separation of concerns, separating UI and network and business logic * Making our code more easily testable * Better unit tests, with less mocking and code units with less scope * Using composition instead of inheritance in the UI components * Declarative UI rendering * Doing away with the direct DOM manipulation paradigm and using a declarative rendering library for the Minerva skin UI components (WARNING) This #epic tasks needs to be revisited when the parent tasks are close to completion and be more concretely specified. It should have a “Progress, Success, and AC” section.

= Documentation on wiki https://m.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture#Review_and_refactor_components = WIP audit of existing MobileFrontend components https://docs.google.com/document/d/1pxTYAu6tIIPR-8TpUJ5_qKdumj8P76k3cbVo-WJAuzU/edit?usp=sharing = What When the previous projects have been successful (see parent task and task graph), we will generate a concrete proposal for this epic. Some goals for this would be: [] Separation of concerns, separating UI and network and business logic [] Making our code more easily testable * Better unit tests, with less mocking and code units with less scope [] Using composition instead of inheritance in the UI components [] Declarative UI rendering * Doing away with the direct DOM manipulation paradigm and using a declarative rendering library for the Minerva skin UI components (WARNING) This #epic tasks needs to be revisited when the parent tasks are close to completion and be more concretely specified. It should have a “Progress, Success, and AC” section.

= Documentation on wiki https://m.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture#Review_and_refactor_components = WIP audit of existing MobileFrontend components https://docs.google.com/document/d/1pxTYAu6tIIPR-8TpUJ5_qKdumj8P76k3cbVo-WJAuzU/edit?usp=sharing = What When the previous projects have been successful (see parent task and task graph), we will generate a concrete proposal for this epic. Some goals for this would be: *[] Separation of concerns, separating UI and network and business logic *[] Making our code more easily testable * Better unit tests, with less mocking and code units with less scope *[] Using composition instead of inheritance in the UI components *[] Declarative UI rendering * Doing away with the direct DOM manipulation paradigm and using a declarative rendering library for the Minerva skin UI components (WARNING) This #epic tasks needs to be revisited when the parent tasks are close to completion and be more concretely specified. It should have a “Progress, Success, and AC” section.