When using the array type, is the type inference incorrect?

[wjp980108]

The issue occurred after updating to version 0.8.1.

In the project：

playground：

[RedStylzZ]

The same happens for me.
My whole project is now full of errors

[xmatthias]

noUncheckedIndexedAccess now defaults to true.

A quick workaround can be noUncheckedIndexedAccess": false in your tsconfig, which reverts the corresponding change (#36) for your project.

---

I think what's worse here is that it also kinda breaks some simple vue concepts and patterns, for example:

<div v-for="(element, i) in somelist">
   <SomeComponent v-model="somelist[i]!"></SomeComponent>
</div>

the (!) is now required - which it really isn't for vue - as we're currently iterating over said list (can't use element in v-model directly, as that causes 'v-model' directives cannot update the iteration variable 'pair' itself.eslint[vue/valid-v-model](https://eslint.vuejs.org/rules/valid-v-model.html)).
If the list would have the element disappear - then the conten of the list would rerender anyway.

[haoqunjiang]

Expected. With as const, you can narrow the type down. Otherwise, the list is mutable, thus any element could be undefined.

const list = ['a', 'b', 'c'] as const
const item = list[0]
//    ^? const item: "a"

[haoqunjiang]

the (!) is now required

Can't reproduce on my machine. vuejs/language-tools has added support for noUncheckedIndexedAccess long ago. If the issue persists, please create a new issue there with reproduction.

[xmatthias]

Can't reproduce on my machine. vuejs/language-tools has added support for noUncheckedIndexedAccess long ago. If the issue persists, please create a new issue there with reproduction.

You'll need the appropriate eslint config for it, which has vue/valid-v-model enabled (for the error when using the element directly).

It's not a vuejs/language-tools issue - but one that's been introduced by tsconfig, really.
Just because you don't seem to use eslint (at least not with vue rules) - or can't reproduce it currently doesn't make it an invalid point that's been introduced by this.

[haoqunjiang]

By "can't reproduce" I mean removing ! won't trigger any error on my side.