Access to getter inside mutation

[Glandos]

Hi, I have the following pattern:

import { VuexModule, Module, Mutation } from 'vuex-module-decorators'
import { Investigation, InvestigationId } from './types'

@Module({ name: 'investigations' })
class Investigations extends VuexModule {
  investigations: Investigation[] = []
  currentInvestigationIndex = -1

  get current (): Investigation | undefined {
    return this.currentInvestigationIndex >= 0 ? this.investigations[this.currentInvestigationIndex] : undefined
  }

  get id () {
    return (id: InvestigationId): Investigation | undefined => this.investigations.find(i => i.id === id)
  }

  @Mutation
  newSequence ({ investigationId }: { investigationId: InvestigationId }): number {
    const investigation = this.id(investigationId)
    if (investigation === undefined) {
      throw Error(`Investigation not found: ${investigationId}`)
    }
    return investigation.sequences.push({})
  }
}

However, when accessing to newSequence, it seems that this.id is undefined. This is not consistent with the behavior with getters nor actions (where it's possible to use context).

Am I missing something?

[weilbith]

I does also not work between getters, doesn't it?

[Glandos]

As far as I remember yes. However, since it was for a new project, I then switched to another helper library (vuex-class-component)

[weilbith]

Yeah, apparently you can't access anything from the class inside getters or other functions (except the "state"). Okay, I'll checkout your option. :+1:

[weilbith]

I'll also look into Vue3 and Vuex4. Let's see.

[davemecha]

It would so great to have a solution for this.

[Glandos]

In fact, I encountered the exact same issue with vuex-class-component, except that I can use a workaround (with proxies).

See my comment on this: it seems that Vuex itself renders this usage quite complicated.

[firstsmarts]

Any progress about this?