To completely refactor the suggested edit module to Vue a state management system is needed to handle the task queue and filters state. Consider using Pinia since it will be available in core after T326174: Add Pinia to MediaWiki core is resolved.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Sgs | T296646 [Epic] Migration of front-end modules to Vue.js components | |||
| Open | Sgs | T329883 Create a state management store for the newcomer task queue and filters |
Event Timeline
Comment Actions
Change 903183 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):
[mediawiki/extensions/GrowthExperiments@master] Frontend documentation: setup Pinia state manager
Comment Actions
Change 903184 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):
[mediawiki/extensions/GrowthExperiments@master] WIP Frontend documentation: create a task feed with a Pinia store
Comment Actions
903183 contains a minimal Pinia setup inside the VitePress frontend documentation. While unified state management is not a requirement for the documentation, adding Pinia to the project would allow to create demos that are closer to a "production ready" state. This task is about the newcomer tasks queue but there are other use cases where Pinia could make sense that were already mentioned in T326233. One use case could be the injection of MW config variables to the different Vue apps from GrowthExperiments. Another could be the user preferences. Another is application state (eg: a replacement for OO.ui.isMobile()). Feedback is welcome.
Comment Actions
Change 903183 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] Frontend documentation: setup Pinia state manager