has some problem in Type Inference

[candy-Tong]

Reproduction

https://github.com/candy-Tong/pinia-demo

I set the Ref<EdgeConfig> type for the edge state. but in action, I use this.edge, the inferred type is not correct, it seems that it says that it reports an error

Steps to reproduce the behavior

1. yarn install
2. npm run tsc

Expected behavior

there is no typescript error

Actual behavior

has typescript error

[BenShelton]

A few things you can try:

1. The documentation for state says that type inference is more reliable when using an arrow function to define state, have you tried that? See https://pinia.esm.dev/core-concepts/state.html#state
2. Instead of using shallowRef you can simply just define the state similar to the following and it'll still be reactive:

state: () => ({
  node: undefined as NodeConfig | undefined,
  edge: undefined as EdgeConfig | undefined
}),

3. Within the action you can type cast the return value:

return this.edge as EdgeConfig | undefined

[posva]

I would personally go with just an arrow function for state. I tested and the type is correct.

[candy-Tong]

I test the arrow function,but it still not corret

[candy-Tong]

1. I test the arrow function,but it still not corret.( I had updated the code to github)
   

2. I want to use shallowRef because i don’t want it to be a deeply reactive object that is a third-party object.

3. Within the action you can type cast the return value. It's work for me. But that means I can't use store.edge directly and must use store.getEdge to get the right type