Kind of have breaking changes for my plugin, it would be nice to have pre update notice before updating.
Which changes are breaking?
obviously the format for encrypted note, we already shifted to markdown from json. we didn't push it to marketplace
Can you elaborate? It’s not really clear what change in Joplin (and in what version) is causing an issue with your plugin
Previously, the encrypted note was packed in JSON format and tag was used to identify.
By looking at most plugins in Joplin, they all are parsing notes and identifying via code fences. This seems to have little performance boots so, we are shifting that model.
Oh, I think you miss understood.
I'm telling, I will be pushing a breaking changes to my plugin. So, I was kind of asking a feature to have a plugin pre update notice for the users.
I see. For a plugin of this nature that’s a significant breaking change to be honest.
Given that the change renders all existing encrypted notes unusable, I’d recommend to add an option within your plugin to prompt to upgrade the format when opening a note in the old format, as I presume the format is specified within the body so can be easily detected. If the format is updated in future versions, you can add a case statement to handle migrations from various old formats.
1 Like