It’s not currently designed for custom fields, so it’s not possible to remove them via
editingNote.update action at the moment.
yep, good point. Cleaning up is important.
The field prefix “x-” is not sufficient for cleaning up.
The plugin name should be able to be inferred by the field names like “x-plugin-name-fieldName”.
But I guess scanning all the notes to clean them up may take a while if the user has a lot of notes.
Another way to store custom data is to create separate docs something like:
The “CUSTOM_DOC_ID” can be arbitrary.
In this way, you can make a doc for each note that has custom data:
In this way, the app can support removing them anytime.
But I need further discussion on this because that makes the app complicated.
The database and sync could be broken.