Try just using books as your data (table data) directly.

Scott

How are you calling your data? Can you show the whole code of your component?

Scott

Can you make a codepen to demonstrate your code and your intentions?

Scott

Unfortunately not. QDatePicker is built for only one single date.

Scott

Um, never done it myself, but if you have control of the content for options with the options slot, couldn’t you create your own select/ deselect “option” within those options?

Scott

I’m still not certain what the use case is. But, how about this? I’m not comparing anything. Just storing the value in a different property.

https://codepen.io/smolinari/pen/XLGMWX

Scott

So, making a selection, yet not showing a selected button? Um, that isn’t a toggle.

Maybe you want QBtnGroup? https://quasar.dev/vue-components/button-group

Scott

Ah. Ok. Like this? https://codepen.io/smolinari/pen/XLGMWX

Scott

Can you try again to explain what it is you are attempting to accomplish? It isn’t quite making sense to me.

Scott

All those files are .js files but for some reason your view of them isn’t showing the file extension. Try turning on file extension names.

I’d suggest you find a different approach to go about your referencing the files. Otherwise you will be losing cache busting capabilities, meaning your users will not be getting newer versions of your app, when you rebuild and publish it.

I’m personally not sure what setting or settings are necessary, but it is Webpack doing the file name hashing/ cache busting.

https://webpack.js.org/guides/caching/

And you can control webpack in Quasar through the quasar.conf.js file.

https://quasar.dev/quasar-cli/cli-documentation/handling-webpack

Scott