Help

• J

  [Solved] Q-toolbar dropdown menu possible ?
  • jctrebalag  

  7
  2
  Votes
  7
  Posts
  3285
  Views

  

  I ended up modifying my approach again slightly to incorporate the ability to include an avatar into the “button”. Specific details are available here: https://forum.quasar-framework.org/topic/2602/image-in-top-dropdown-menu/2 The short of it was to use a q-chip with avatar set to the image and no content – then use the clever popover approach above.
• 

  How can I access vue instance?
  • danielsalles  

  9
  1
  Votes
  9
  Posts
  5867
  Views

  

  @rstoenescu Oh, my bad. I had added in components. Now I’ve got it, and it’s working. Many thanks for the support offered
• 

  Using firebase as plugin in Quasar 0.15
  • CristalT  

  8
  0
  Votes
  8
  Posts
  5135
  Views

  

  The error is not related with repo. Quasar CLI uses yarn to create the project. The node version you have is incompatible with the installed yarn version. As log says, the node version must be “>=4 <=9” I’ve experimented the same error on my local since ago. I recomend you change the node version. If you have nvm, it could be very easy. Then reinstall Yarn and Quasar CLI under new node version selected; 8.9.0 will work. Hope it helps you.
• J

  Using global lodash with quasar v15 (Solved)
  • jeimz173  

  7
  0
  Votes
  7
  Posts
  4105
  Views

  T

  I ended up doing this in my plugin file. This makes it globally available. // import something here import _ from 'lodash'; // leave the export, even if you don't use it export default ({ app, router, Vue }) => { window._ = _; }; And then add globals: { 'ga': true, // Google Analytics 'cordova': true, '$axios': true, '_': true, '__statics': true }, into .eslintrc.js. So the linter doesn’t complain. One has to restart quasar dev to reload the .eslintrc.js file. After that one can use lodash as usual just by typing _.
• L

  separator between toggle buttons
  • lazaroofarrill  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• S

  Collapse into two tabs
  • SeRiusRod  

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• Y

  Set capacitor's default server URL?
  capacitor development server config • • yhu420  

  3
  0
  Votes
  3
  Posts
  12
  Views

  Y

  Thank you for pointing this out. Since no solution exist yet, I’ll open a github issue about this. Thank you for your input.
• I

  SSR Deployment(Vercel / Netlify)
  deployment ssr • • IO2021  

  2
  0
  Votes
  2
  Posts
  10
  Views

  

  Netlify only support next.js SSR deployment. I don’t know about vercel. https://www.netlify.com/blog/2020/12/07/announcing-one-click-install-next.js-build-plugin-on-netlify/
• C

  i18n with SFC
  • Clareon  

  7
  0
  Votes
  7
  Posts
  46
  Views

  C

  SOLVED: <i18n> Single File Components Thank you all for advice and help. There are two things in the quasar docs I stumbled: 1 Under Quasar Options and Helpers there is an entry for App Internationalization (i18n). There is a header Setting-up-Translation-Blocks-in-your-SFCs. The description says: “you must ensure that the @intlify/vue-i18n-loader and …”. The example that shows the change for the quasar.conf.js file says { loader: '@kazupon/vue-i18n-loader' }, The description wants the new intlify and the example shows the kazupon. 2 In the same document down there is a header Create language switcher. At the end of the example there is a watch: watch: { lang(lang) { this.$i18n.locale = lang } } This works good for all texts in the given one component. If you want to change the language for all components in your app you have to do this: this.$root.$i18n.locale = lang; Important is inserting $root between this and $i18n. Perhaps anyone is able to change the docs. Thank you.
• A

  Starting a new project
  • archimede  

  3
  0
  Votes
  3
  Posts
  27
  Views

  A

  Hi and thanks for taking time to reply. Indeed I don’t NEED vue3, but I thought it would be a good idea starting with it to avoid potential problems later on. I gather from your answer no major issues are expected migrating from the current stable version to the future vue3 implementation (especially for small projects like mine): therefore I’ll follow your advice and stick with the current stable release. Thanks again for your help. Alessandro
• M

  Access LocalStorage at startup
  • MeeSha  

  4
  0
  Votes
  4
  Posts
  13
  Views

  R

  You did not mention what file your mounted() code was in. I would suggest the code be placed in App.vue.
• S

  QSelect not updating when default value is set
  • smaldona  

  5
  0
  Votes
  5
  Posts
  109
  Views

  C

  @smaldona Thanks so much for this! I’ve adapted it to default a q-option-group to also have a default value, as I’ve been looking for this. <q-option-group v-model="buriedModel['buriedOff']" :options="buriedOff" color="primary" inline /> data() { return { buriedModel: [], buriedOff: [ { label: 'Yes', value: 'Yes' }, { label: 'No', value: 'No' } ] } } this.$set(this.buriedModel, 'buriedOff', 'No') // set radio button default to No
• S

  Not mutating prop, still get an error
  error prop • • szabiaura  

  5
  0
  Votes
  5
  Posts
  20
  Views

  S

  @dobbel Thanks, that almost did it. For the perfect solution you need @Prop({ type: Boolean, default: false }) readonly withAdd!: boolean;
• C

  How to set default value in q-option-group
  • cynderkromi  

  3
  0
  Votes
  3
  Posts
  9
  Views

  C

  @dobbel Thanks. The option list will be part of a form that will be submitted and saved to IndexedDB. And I will have a page that will be able to update the values, too. So I need to work out all those details. I do want the radio button list to default to No when the page initially loads.
• S

  Recommendations on App architecture
  • SeRiusRod  

  20
  0
  Votes
  20
  Posts
  97
  Views

  S

  Okey. I was getting a silent Cors error.
• M

  PWA + Typescript
  build pwa typescript • • MartinB  

  5
  0
  Votes
  5
  Posts
  28
  Views

  S

  Created this issue: https://github.com/quasarframework/quasar/issues/8340 this github repo to reproduce: https://github.com/sluedecke/quasar-pwa-test
• M

  Vuex Getters and Typescript errors
  • matt-h  

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• O

  Can't get value of a state in vuex store
  • oussama-he  

  2
  0
  Votes
  2
  Posts
  13
  Views

  

  @oussama-he most important file you did not list: src/store/index.js don’t put the mapState into data data() { return { ...mapState('example', ['projects']) }; }, instead put the mapped state into the computed section computed: { ...mapState('example', ['projects']) }
• N

  Closing a q-dialog with a lot of content is very very slow
  • nulele  

  3
  0
  Votes
  3
  Posts
  16
  Views

  

  @nulele If possible, please make a code pen of the issue, or share some of the code for CustomComponent. You could maybe try using <CustomComponent v-once ...></CustomComponent> But I’m not sure how that would affect your component without seeing it. There must be some heavy data-reactivity going on, I would suspect.
• B

  Trouble Accessing Data from Boot File
  • bdaviddee  

  11
  0
  Votes
  11
  Posts
  593
  Views

  P

  @metalsadman said in Trouble Accessing Data from Boot File: store = Store Exposing the store worked out for me as well. Thank you.