You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks again for your amazing work on vue-tsc, nothing is greater than to be type safe in a Vue environnement.
In our codebase we want to gradually make component imports safer, and currently an undeclared Component is marked as unknown.
Activating strictTemplates: true resolve this, but also activates the strict prop typechecking, which we currently can't handle in our codebase.
We are then currently blocked on this subject as we would like to gradually upgrade a safer props types but will be too much work for now.
What does the proposed solution look like?
The solution could be to split the strictTemplate into two options, or to add a two new ones strictProps and strictComponentImports, to cherry pick which one we want.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
First, thanks again for your amazing work on vue-tsc, nothing is greater than to be type safe in a Vue environnement.
In our codebase we want to gradually make component imports safer, and currently an undeclared Component is marked as
unknown
.Activating
strictTemplates: true
resolve this, but also activates the strict prop typechecking, which we currently can't handle in our codebase.We are then currently blocked on this subject as we would like to gradually upgrade a safer props types but will be too much work for now.
What does the proposed solution look like?
The solution could be to split the
strictTemplate
into two options, or to add a two new onesstrictProps
andstrictComponentImports
, to cherry pick which one we want.The text was updated successfully, but these errors were encountered: