Open alwun opened 11 months ago
I'm having the same issue, and have also seen other users run into this on the Obsidian discord.
I found out some more about this. So, there's some migration that is supposed to occur so the macro is referred to by an ID, rather than embedding a copy of the macro into the choice. There seems to be an issue with this migration process, which causes this bug.
At first, I thought there might be some issue with the macro-ids not matching, but I confirmed that this is not the case in data.json.
I found the following workaround, which seems to solve the issue:
"migrations": {
"migrateToMacroIDFromEmbeddedMacro": true, // set this to false
I don't know what the potential ramifications of this are, but hopefully @chhoumann can tell us more.
Describe the bug Any macro that is modified after the quick entry is enabled does not automatically update itself.
To Reproduce Steps to reproduce the behavior:
Create a new macro and enable quick entry for the macro
![image](https://github.com/chhoumann/quickadd/assets/76609616/4a2f4530-6fd6-4768-a8c1-c854c10ab61a)
Modify the macro![image](https://github.com/chhoumann/quickadd/assets/76609616/92d37250-add2-422b-8ac8-e0b5f70f702d)
Run macro from command palette![image](https://github.com/chhoumann/quickadd/assets/76609616/a5069413-a392-4507-a888-544df5817d65)
The macro does not update itself, displaying error![image](https://github.com/chhoumann/quickadd/assets/76609616/5402cc29-3fd4-4459-822a-76ed89deeaff)
Expected behavior The macro's quick entry should automatically update when the macro is modified
Additional context The only way to update the macro is to disable the quick entry option and re-enable it after changes are made.