Page MenuHomePhabricator

[WtC-M1] Migrate to Pinia
Closed, ResolvedPublic8 Estimated Story Points

Description

Problem

In order to migrate the Mismatch Finder's code base away from Vue 2 to Vue 3 and avoid the consequences of Vue 2's EOL, we will have to migrate various peer dependencies such as Vuex (@3.6.2).

Solution

As part of the preparation work to migrate the Mismatch Finder's front-end from Vue to Vue Compat layer, we'll replace Vuex by Pinia. The latter store library brings certain advantages, such as a simpler API or better Typescript support.

Acceptance criteria
  • Install @vue/composition-api
  • We migrate from Vuex to Pinia
  • Typescript incompatibilities are fixed
  • Relevant code points are updated
Notes

Event Timeline

Sarai-WMDE renamed this task from [WtC-M1] Migrate to Pinia to [SW] [WtC-M1] Migrate to Pinia.Sep 26 2023, 4:40 PM
Arian_Bozorg renamed this task from [SW] [WtC-M1] Migrate to Pinia to [WtC-M1] Migrate to Pinia.Sep 28 2023, 2:40 PM
ItamarWMDE set the point value for this task to 8.Oct 4 2023, 8:20 AM

Potential Plan Action:

  1. Install the package
  2. Change the actual code after installing the package (mutations to actions, usage in componenets, init in store/index.ts)
  3. Remove Vuex
  4. Fix what's broken with Typescript

I think we should migrate to Vue@3 first because we are having issues with multiple composition-api instances with current vue@2.6 setup. There are different versions of composition-api, it makes another mess.
Further info: https://github.com/vuejs/composition-api/issues/792