How to handle projects which have common sections
-
I have a project created with quasar-cli. Now, I want to make some projects Which are almost similar to this project ,however, it also faces with some differences in pages,routes,stores and etc. These projects will definitely become updated in common and separate sections. The question is that what will be the best solution for handle such projects in case of saving time and coding?
-
@mohamadJ You can copy your folder’s content into your new project, fix the correct paths,references etc. a decent free ide like vscode is enough to help you keep track of those. easiest if the new project is using qcli, if not then i can only see that would pose an issue is in the quasar app extension side (it only works at qcli atm), probably some tweak for the configs as well(check how to set it https://quasar.dev/start/umd or if you use quasar as vue plugin at https://quasar.dev/start/vue-cli-plugin).
-
I haven’t done this yet, but you should be able to use a starter site plus a stable set of components that you don’t edit between projects, but only extend or use. See https://vuejsdevelopers.com/2017/06/11/vue-js-extending-components/
-
@metalsadman and @dnix thank you for reply. I use a quasar ext for common sections such as components, boots, stores and etc. Each new project have own pages and other uncommon sections.All of them use this extension.
-
@mohamadJ nice, that’s a neat solution.
-
Quasar App Extensions is the way to go. It’s one of its maaany purposes.
