-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typing regression on "useI18n()": spyOn return "never" type #1562
Comments
Would you be able to provide a reproduction 🙏 More infoWhy do I need to provide a reproduction?Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. What will happen?If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If How can I create a reproduction?We have a couple of templates for starting with a minimal reproduction: 👉 Reproduction mininal starter A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as minimal as possible. You might also find these other articles interesting and/or helpful: |
I created a repo with minimal configuration git clone git@github.com:pinguet62/vue-i18n--typing-regression.git
cd vue-i18n--typing-regression
npm ci
npm run type-check
|
🖖 Any news? |
Reporting a bug?
After upgrade from
9.3.0-beta.27
, the mock ofuseI18n()
doesn't work:throws
Property 'mockReturnValue' does not exist on type 'never'.
Expected behavior
No error :)
Reproduction
npm install vue-i118n
npm run type-check
System Info
Screenshot
No response
Additional context
Seems be a regression in #1309 7ebb0e4#diff-90783ef144f3a897c890355ff61bd08a99bbd36764128426b6f899a72e766f2eR803
Reverting line to previous version
NonNullable<Options['locale']>
seems fix the problem.Like the
test:type
checks are still OK, probably the current typing is too strict? 🤔Validations
The text was updated successfully, but these errors were encountered: