Oh cool, I didn’t realize you can inspect like that. I usually just have the console open then click the select element icon.
Dense looks like it should work for me too. Thanks for your help.
When using QSelect, how can I set the height of the entire control? If I set the height of the label, then it appears to be the correct size, but maintains additional space below it down to where the bottom border is. If I add borderless then visually it looks right, but the space is still preserved and leaves the options offset.
I can’t seem to inspect the options element or snip a screen shot of it since it closes after it loses focus. Here’s the codepen though. I made the background blue so that it is easier to see the gap between the options and the dropdown.
@RishitKedia Can you go into any more details about how to go about getting started making a chrome extension that uses quasar?
Or do you think you could possibly make a starter kit by removing all of the functionality from tabtation and just give us the basic setup for quasar?
I’d really like to use quasar in my chrome extension but I am having a really hard time getting started.
I was able to hack this to work locally by changing the actualValue computed property in QDatetime.js to just return the value, since I know I am setting it correctly.
//return formatDate(this.value, this.computedFormat, /* for reactiveness */ this.$q.i18n.date)
However, now I don’t know how to keep that change in my netlify deployments.
I think it has something to do with using dashes vs slashes, but according to the documentation it should work if I provide a format.
It also only happens on months that have a leading 0…
For some reason, when I set the model programmatically (vs manually picking the date), the datetime input component displays the selected date as 1 day earlier, bur it has a value of the correctly selected date when I inspect it in vue dev tools. How can I get this to display the correct date (e.g. the assigned value of the model)?
<q-datetime v-model=“from” type=“date” format=“YYYY-MM-DD” minimal/>
I am using framework v0.17.20 (cli 0.17.24) and I added ‘QToolTip’ to my framework components in quasar.conf.js the same way I have done with dozens of other quasar components. However, when I add QToolTip, I get the following error:
ERROR Failed to compile with 1 errors 08:03:01
error in ./.quasar/import-quasar.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Unknown import from Quasar: QToolTip
How can I add that .htaccess file to my build folder automatically?
That’s perfect, thank you.
@qyloxe I’m using git. Since posting this, I’ve been made aware of Netlify, which seems like it could solve this problem for me (automating deployment based on bitbucket pushes), but so far I haven’t been able to get the build to register as successful.
I made this question about it on Stack Overflow: https://stackoverflow.com/questions/54772505/how-do-i-deploy-a-quasar-framework-spa-using-netlify
I have a component that renders a dynamic list that includes an action button for each list. For :loading on that button I use a global inProgress variable that is set to true before my post request, then it is set to false when the request receives a response. This works great, except that it makes all the buttons spin like they are loading whenever 1 is hit.
Do you guys have a good pattern for using keyed loading parameters or something?
How do you guys handle your deployments?
My current workflow feels a bit clunky.
I am mainly making internal tools for a small group of users, so it is working so far… I’m just wondering if I am missing out on a better deployment strategy. I’m using SPA if that matters.
I agree with your desire to end his Tyranny, though part of me secretly thinks I should just give into it.
The Apache version from @damosse31 worked for me, thanks.