Consider transferring a template containing modules of path src_modules/module_x and src_modules/module_y from one account (account_a) to another (account_b) where it already have modules with same name but different path as follows des_modules/module_x and des_modules/module_y This activity currently pops out an error stating Error: Asset not found and in network it shows "errorCategory": "THEME_NOT_FOUND" . Workaround: change the module name and the corresponding path would now be src_modules/module_x_new and src_modules/module_y_new . when we try to copy the template containing these modules to another account (account_b), it shows success and new modules created with the exact path. Goal: It will be a great feature if we get to transfer template across accounts even when there is a file with similar name existing in destination account but in different folder name (technically it will have a different path). For instance, take the above scenario where moving src_modules/module_x and src_modules/module_y from account_a to accout_b can be allowed where it would have created the files properly without any conflict (since they are in different folders and path also differs) and stayed off from des_modules/module_x and des_modules/module_y.
... Afficher plus