Has it ever worked?
You can try
npx quasar create foo
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