This is probably a looped question about Dropbox and the sync feature, but I did not find an answer for this detail :
I understood that Joplin and Dropbox presently exchanges a token for an authorization to only sync in Applications/Joplin folder. Fine!
Joplin is allowed to create its own structure inside this specific third-party folder, i.e. creating its own folders as .lock, .resource, .sync, locks, temp, ...
Then, my question is :
What prevents Joplin to create the profiles folders (as for example already done in JoplinBackup folder structure) inside Applications/Joplin folder before doing the corresponding syncs for each profile.
i.e. Applications/Joplin/Profile1/, Applications/Joplin/Profile2/, etc. folders
The benefit would be to sync multiple profiles in the same Dropbox account (without the merging issue of multiple profiles that we have with present sync implementation) !
In the Option menu for Dropbox sync target, it would eventually require to ask the user (after token approval) which existing profile folder to sync with, or create a new folder if necessary...