Open zsviczian opened 3 years ago
Looking at data.json this looks very doable... even, dare I say, easy. The .js scripts could be added to the JSON (for the purpose of export/import). You'd need to build a dependency tree of macros, commands, choices, to filter data.json for the export. The headache will be handling updates / new versions of scripts... but if you keep the GUIDs unchanged, then you can overwrite the previous entry, plus you can simply overwrite .js scripts with a prior warning of course.
You could develop a "marketplace" of quickadd packages under discussions/show&tell much like Templater, but with the package import/export it would be much more accessible to less experienced obsidian users.
Hey! This has been the intent from even before I started coding. It's also why everything is formatted as it is. It's also one of the next features coming.
Is this possible today somehow?
Describe the solution you'd like It would be great if I could export selected macros to a file (including the .js script components), and import those macros as a package to another Obsidian Vault. This would be kind of a plugin within the plugin support. Such an export/import approach would allow sharing of automation macros with users who are not familiar with programming but would like to reuse scripts in their own workflow. It would also allow moving automation between my own vaults.
Additional context See comment by user on this video: https://www.youtube.com/watch?v=b6jhQrRMTvs