Don't get autocomplete/intellisense when using "this" in store actions

[gunhaxxor]

According to the documentation I should get type support when writing "this" in store actions. Doesn't seem to work for me. What am I doing wrong. Thankful for any advice!

It's described here

Like getters, actions get access to the whole store instance through this with full typing (and autocompletion ✨) support.

[posva]

You might be missing a config file for TS to work because it does autocomplete on my end. Maybe jsconfig.json?

[gunhaxxor]

Well. I do get partial intellisense:

It's really weird! I should mention that I'm trying to set up pinia within a quasar v2 typescript project.
I should also mention that I get no errors from typescript compilation, only missing intellisense inside editor.
Here's my eslintrc.js:

const { resolve } = require('path');
module.exports = {
  // https://eslint.org/docs/user-guide/configuring#configuration-cascading-and-hierarchy
  // This option interrupts the configuration hierarchy at this file
  // Remove this if you have an higher level ESLint config file (it usually happens into a monorepos)
  root: true,

  // https://eslint.vuejs.org/user-guide/#how-to-use-custom-parser
  // Must use parserOptions instead of "parser" to allow vue-eslint-parser to keep working
  // `parser: 'vue-eslint-parser'` is already included with any 'plugin:vue/**' config and should be omitted
  parserOptions: {
    // https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/parser#configuration
    // https://github.com/TypeStrong/fork-ts-checker-webpack-plugin#eslint
    // Needed to make the parser take into account 'vue' files
    extraFileExtensions: ['.vue'],
    parser: '@typescript-eslint/parser',
    project: resolve(__dirname, './tsconfig.json'),
    tsconfigRootDir: __dirname,
    ecmaVersion: 2018, // Allows for the parsing of modern ECMAScript features
    sourceType: 'module' // Allows for the use of imports
  },

  env: {
    browser: true
  },

  // Rules order is important, please avoid shuffling them
  extends: [
    // Base ESLint recommended rules
    // 'eslint:recommended',

    // https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin#usage
    // ESLint typescript rules
    'plugin:@typescript-eslint/recommended',
    // consider disabling this class of rules if linting takes too long
    'plugin:@typescript-eslint/recommended-requiring-type-checking',

    // Uncomment any of the lines below to choose desired strictness,
    // but leave only one uncommented!
    // See https://eslint.vuejs.org/rules/#available-rules
    // 'plugin:vue/vue3-essential', // Priority A: Essential (Error Prevention)
    // 'plugin:vue/vue3-strongly-recommended', // Priority B: Strongly Recommended (Improving Readability)
    'plugin:vue/vue3-recommended', // Priority C: Recommended (Minimizing Arbitrary Choices and Cognitive Overhead)

    'standard'

  ],

  plugins: [
    // required to apply rules which need type information
    '@typescript-eslint',

    // https://eslint.vuejs.org/user-guide/#why-doesn-t-it-work-on-vue-file
    // required to lint *.vue files
    'vue',

  ],
  "overrides": [
        {
            "files": ["*.ts"],
            "rules": {
                "no-undef": "off"
            }
        }
    ],
    
  globals: {
    // SocketExt: ''
    // SocketServerEvent: 'readonly',
    // SocketAck: 'readonly',
    ga: 'readonly', // Google Analytics
    cordova: 'readonly',
    __statics: 'readonly',
    __QUASAR_SSR__: 'readonly',
    __QUASAR_SSR_SERVER__: 'readonly',
    __QUASAR_SSR_CLIENT__: 'readonly',
    __QUASAR_SSR_PWA__: 'readonly',
    process: 'readonly',
    Capacitor: 'readonly',
    chrome: 'readonly'
  },

  // add your custom rules here
  rules: {
    // allow async-await
    'generator-star-spacing': 'off',
    // allow paren-less arrow functions
    'arrow-parens': 'off',
    'one-var': 'off',
    'no-void': 'off',
    'multiline-ternary': 'off',

    
    quotes: [2, "single", { avoidEscape: true }],
    semi: [1, "always"],
    indent: [1, 2],
    "no-unreachable": 1,

    'import/first': 'off',
    'import/named': 'error',
    'import/namespace': 'error',
    'import/default': 'error',
    'import/export': 'error',
    'import/extensions': 'off',
    'import/no-unresolved': 'off',
    'import/no-extraneous-dependencies': 'off',
    'prefer-promise-reject-errors': 'off',

    "vue/max-attributes-per-line": ["error", {
      "singleline": 4,
      "multiline": {
        "max": 1,
        "allowFirstLine": false
      }
    }],

    "comma-dangle": ['warn', 'always-multiline'],

    
    "vue/component-name-in-template-casing": ["error", "PascalCase"],

    // TypeScript
    quotes: ['warn', 'single', { avoidEscape: true }],
    '@typescript-eslint/explicit-function-return-type': 'off',
    '@typescript-eslint/explicit-module-boundary-types': 'off',
    
    // warning instead of error
    "@typescript-eslint/ban-types": [
      "warn",
      {
        "extendDefaults": true,
      }
    ],

    "@typescript-eslint/no-unsafe-assignment": "warn",

    // allow debugger during development only
    'no-debugger': process.env.NODE_ENV === 'production' ? 'error' : 'off'
  }
}

[gunhaxxor]

Damn. Restarted my editor and suddenly it works. Not sure how or why it didn't work at first. But now it does ✨

[sisou]

I just ran into this issue, too. Due to the huge codebase (updating from v0.0.5 to latest v1), I did not immediately see the type error in the beginning of the log.

Turns out we are on a too old @vue/composition-api version also. Pinia requires at least v0.6.0, but we are on v0.4.0. Would be cool if pinia could specify this dependency as a peerDependency so that I get a warning when running npm or yarn.

Anyway, seems I have to update the composition-api... the biggest problem is all the watchers, that are then lazy by default... who will test all the flows? :/

[h-guliyev]

I have also a weird issue in my Typescript project. Intellisense works inside actions, but inside getters it can't see any of actions.

[posva]

this is normal, you shouldn't access actions inside getters because they are side-effect free

[tslocke]

In case it helps anyone else, I had the same problem and fixed it by switching strict: false to strict: true in tsconfig.json