This is the greatest thing I’ve built in months. So stoked and thank you to @metalsadman for helping me get it the last mile. This completely changes how I will manage my data models going forward!

General idea is that you define your form fields as schema. Your Form component will iterate these field definitions and the Field component will render the specified UI component with all the settings specified. It’s beautiful in action. You can use ANY UI component you want.

You will need to include any UI component you render this way in the components section of your quasar.conf file. Even if you have importStrategy set to ‘auto’. That only works when the components are visible in the template when being rendered. Since this is dynamic that no longer works

Gist

I was refactoring today and ended up completely revamping my Axios configuration to reduce all of my duplicate code. Really happy with it!

• Default headers but specific to http methods
• Request interceptor for logging
• Response interceptor for logging

Gist

I never found an answer documented but I think my hunch worked.

import { mountFactory } from '@quasar/quasar-app-extension-testing-unit-jest'
import {
   QMenu,
   QList,
   QItemLabel,
   QItem,
   QItemSection,
   QIcon,
   QBtn,
   ClosePopup,
} from 'quasar'
import HelpMenu from '../../../../src/components/menus/HelpMenu.vue'

const $t = jest.fn()
// $t.mockReturnValue('')

const factory = mountFactory(HelpMenu, {
   mount: {
      mocks: { $t },
   },
   quasar: {
      components: {
         QMenu,
         QList,
         QItemLabel,
         QItem,
         QItemSection,
         QIcon,
         QBtn,
      },
      directives: {
         ClosePopup,
      },
   },
})

describe('HelpMenu', () => {
   test('mount w/o error', () => {
      console.log(factory())
      expect(factory).toBeTruthy()
   })
})

I no longer see the error message.

Ha… I went there and saw a single post that was deleted. I misread that the category itself was removed. Thanks for pointing out the obvious for me!

I have been working on a (closed) project for several months now. It is a consumer-facing application that is currently constrained to US customers. I’m looking for help from a senior, full-stack developer with experience building web and native apps (Electron & Cordova) with Quasar, Firebase, and Auth0. I have a software company that I started in 2014 but retired last year and this is my first project since (this project is not related to my previous business). It’s my first time building a full-stack application. It is very important that you already have this experience and can hit the ground running. I want you to start with a full code review and a write-up detailing thoughts on the project and the current state of the code. That write-up would determine the next steps (think of it as a competition). I’m open to a fixed fee engagement for the initial review and then an hourly rate moving forward. If you are interested, send me an email with your relevant experience and any questions you need from me in order for you to provide a work order for the initial review. I prefer someone living in the Western Hemisphere for time reasons. I am in the US in the Central Time Zone. If you have any other questions feel free to PM me here before submitting an email response. Thanks! troy@34fame.com

I did submit to #jobs channel on Discord but was going to put out here in forums as well, if appropriate.

https://quasar.dev/quasar-cli/installation

Has it ever worked?

You can try npx quasar create foo

The write up I promised!

https://medium.com/@graypes/add-dynamic-forms-to-your-vue-app-609de4005a2b

Great ideas, @dobbel ! For now my focus has been on the rendering and, since this post, I’ve been able to add more complex use cases. Now I can handle rendering of nested components, all dynamically. This was actually my ultimate goal. I’ll be posting a full story on it soon.

@qyloxe There are many good solutions for rendering forms but none that I found met my criteria. The big one was being able to render simple AND nested components completely dynamically. In other words, I don’t need to build a component template and pass in props. The whole thing is dynamically generated!

This is the greatest thing I’ve built in months. So stoked and thank you to @metalsadman for helping me get it the last mile. This completely changes how I will manage my data models going forward!

General idea is that you define your form fields as schema. Your Form component will iterate these field definitions and the Field component will render the specified UI component with all the settings specified. It’s beautiful in action. You can use ANY UI component you want.

You will need to include any UI component you render this way in the components section of your quasar.conf file. Even if you have importStrategy set to ‘auto’. That only works when the components are visible in the template when being rendered. Since this is dynamic that no longer works

Gist

I was refactoring today and ended up completely revamping my Axios configuration to reduce all of my duplicate code. Really happy with it!

• Default headers but specific to http methods
• Request interceptor for logging
• Response interceptor for logging

Gist