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
Bottom sheet action is missing property "id" #11924
Labels
area/plugins
area/typescript
bug/2-confirmed
We have reproduce the problem and confirmed that this is a bug.
kind/bug 🐞
Qv2 🔝
Quasar v2 issues
Comments
Please change the title to request changes in TS definition to allow extra properties in actions objects |
yusufkandemir
added
kind/bug 🐞
area/typescript
bug/2-confirmed
We have reproduce the problem and confirmed that this is a bug.
Qv2 🔝
Quasar v2 issues
area/plugins
labels
Jan 6, 2022
rstoenescu
added a commit
that referenced
this issue
Jan 7, 2022
There's no need for the |
rstoenescu
added a commit
that referenced
this issue
Jan 7, 2022
Labels aren't necessarily unique. A unique identifier for each option would be valuable. |
Will be available in Quasar v2.4.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/plugins
area/typescript
bug/2-confirmed
We have reproduce the problem and confirmed that this is a bug.
kind/bug 🐞
Qv2 🔝
Quasar v2 issues
Describe the bug
The "id" property is missing on the actions type for Bottom Sheet. The API shows no "id" field under actions https://quasar.dev/api-explorer#api--bottomsheet
Codepen/jsFiddle/Codesandbox (required or your issue may be closed)
Everything works if you ignore the typescript warnings https://jsfiddle.net/pm4v0jg9/1/
To Reproduce
Steps to reproduce the behavior:
Copy paste the examples for how to use the component here: https://quasar.dev/quasar-plugins/bottom-sheet#usage
Implement in your IDE with any typescript validation
Expected behavior
No errors
Screenshots
Platform (please complete the following information):
Quasar Version:
@quasar/app Version: 2.4.3
Quasar mode:
Additonal Info:
<script setup>
Tested on:
OS: OSX 12.0.1
Node: 16.13.0
NPM: 8.1
Yarn:
Browsers: Chrome
iOS:
Android:
Electron:
Additional context
This issue could have been posted in the incorrect docs folder, but i think this variable is very valuable as no other reliable identification for the selected answer is available
The text was updated successfully, but these errors were encountered: