-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Types of QUploader instance properties are missing #13217
Comments
QInput is also missing instance property types #11510. I am linking it here because they are related. |
Fix will be available in Quasar v2.8 |
not fixed 2.8.2! |
@paperisque it would have been more helpful if you share what's not fixed. But, |
For anyone else that comes across this: Volar doesn't automatically pick up changes to |
sorry, yes I meant "isUploading". I am waiting 2.8.3
|
What happened?
The
QUploader
scoped param is not fully typescript-ready. I used the official example for QUploader custom header and although some properties are already properly typed, others from the example are missing, notably:What did you expect to happen?
The official custom header example (and others) should work as-is with TypeScript. All the properties available on scoped params should be properly typed.
Reproduction URL
https://github.com/paya-cz/quasar-scoped-param-typescript-issue
How to reproduce?
src/components/ExampleComponent.vue
using Visual Studio Code<template>
sectionNotes:
npm init quasar
with Quasar v2, TypeScript, CLI+Vitenpm init quasar
that you can inspect to see the diff, but it is just a copy/paste of the QUploader exampleFlavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
TypeScript Support
Platforms/Browsers
No response
Quasar info output
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: