Q-Table component has an issue in initialization. #11279
Unanswered
Claus1
asked this question in
Ideas / Proposals
Replies: 2 comments
-
|
Hi, Attaching a codepen or codesandbox link of your scenario will be infinitely more helpful for people to offer assistance. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks! I found the solution with Composition api, with clear Option API it was impossible. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My custom table uses Q-Table and on load I have to load 'selected' property from my data.
I make computed rows() which makes rows from my data. And I have to initialize 'selected' property from the 'rows', because q-table requests its objects. If it works with key it would be normal, but how to make it without conflict?
Ok, do it in mounted(). I have a watcher for selected and such init in mounted() causes watch handler, but 'selected' value did not changed. It's init value . So if you see good way to get round the issue, I will glad to hear)
Beta Was this translation helpful? Give feedback.
All reactions