Should had tried that before.
Another valid situation: I have a server framework and doing several different apps on same server base, and those apps share some boot files that embed common framework logic and each one still have some exclusive boot files that is individual app logic.
I suggest that quasar should look for a folder “common” (this name should be configured in quasar.conf) one path up from the project folder, and if it is founded, folders with same name than the ones created on the project folder should be used / recognized.
+ server - client - _common // or "global" or "global_src" + boot // recognised: global boot files + assets // recognised: global assets files + my_folder // ignored OR could be used for imports - quasar_app_1 - src + assets + boot + etc + quasar_app_2 + quasar_app_N
I have different client versions, some with more some with less features for the same server app.
Think like if it is an app for enterprise management (this is the server) and I have different clients for different areas of the enterprise, each one seeing very different aspects of the same app, and thus, sharing a lot of technical stuff (like boot files, for example).
Hi. I have multiple sub apps in a structure like this:
+ server + client + _common + wish_global_boot_files_were_here + quasar_app_1 + assets + boot + etc + quasar_app_2 + quasar_app_N
Then I have some boot files that I want to use among the “quasar_app”'s fellows, doing that by placing them on a folder in “_common”.
How to do it?
Hi all. This is quite a “downgrade” IMHO.
Having the old :filter=“true” used to do the job for the vast majority of the needs.
In my case, with a dynamic form where components are only known when they’re needed, I do not have the “data” under my control as it is dynamic and change from form to form.
The filterfn example assumes a known “stringOptions” to be present, but with dynamic forms you simply dont have this.
Any way to get the old behaviour back?
Thank you for share your find
@azeredobr I’m not doing this with quasar yet. I have it done on another project and I was hopping that quasar would bring this by default, so I wouldn’t need to re implement it by myself again.
I think the best way to this would be two complete separated but, of course related implementations: