njtynhj

Multi tool use

I have run into some odd behaviour with v-select and v-data-table that I cannot figure out. The issue is with model bindings to hold the selection of given v-select component when presented for each row in a v-data-table. It's not clear whether I'm using the model bindings in a way that does not play well with Vuetify (model bindings are stored in an object, keyed by item ID), or whether this is a legitimate defect with the v-select component.

The issue only seems to happen when the multiple feature is enabled on a v-select component. The issue is demonstrated in this Codepen: https://codepen.io/dkichler/pen/gKBZLR

It can be demonstrated by choosing a selection for one of the rows, and then attempting to change the sort order (by Name, for example). The table using single selection v-selects reorders and maintains selections with the appropriate row, as expected, but the multiple selection v-select table does not, and instead throws a TypeError:

[Vue warn]: Error in callback for watcher "inputValue": "TypeError: Cannot read property 'findIndex' of undefined"

Hoping someone has the expertise to help me sort out whether I'm using these components incorrectly, there is a more appropriate way to achieve the same thing, or there is a legitimate bug in v-select.

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.