Strict templates should report unknown events

[IceBlizz6]

Strict templates reports unknown components and unknown props.
I would also like it to report unknown events.

<router-link
    to="/contact"
    @eventDoesNotExist="doSomething"
>
    Text here
</router-link>

In this example vue-tsc should report an error which states that eventDoesNotExist is not defined on router-link.

[IceBlizz6]

@so1ve
I would love for this to get some attention, but i also suspect that there are many other more important issues.
I wanted to look into the possibility of fixing this myself, but have not touched this code base before.
Would you be able to give me some pointers on where in this code base that i could start in order to fix this?

[so1ve]

You can install the Volar labs extension then you can inspect the generated virtual code in your sidebar.

[so1ve]

I've tested locally and this seemed to work

[IceBlizz6]

tested locally and this seemed to work

Thanks a lot!
Are you planning to merge this into the next version?

[so1ve]

Sorry, I couldn't explain it clearly. I mean vue-tsc has currently reported unknown events (with strictTemplates: true 💦

Oh it doesn't report when I add a to prop

[IceBlizz6]

I tested it now,
you're right, this actually works when no props are present.
And then it stops working when props are assigned.

So it seems like the current behavior is bugged.

[IceBlizz6]

Maybe we should remove the 'enhancement' tag,
replace it with a tag indicating that this is a bug.

[IceBlizz6]

Hey @so1ve

There hasn't been any updates on this recently.
Strict mode is very important for us and it would be great to see a fix soon.

If you are busy with other things then i completely understand,
But in that case maybe you could point us to another developer which may be able to assist.

[IceBlizz6]

I'd hate to bump this again, but would be great if someone could look into this bug.
It's an important feature and it's broken.
We have a working reproduction.
Is there anything else i can provide?

[IceBlizz6]

Hey @so1ve
Did you figure out a solution here?

[so1ve]

Unfortunately I didn't, my solution breaks vue 2.7 tests.