[QUESTION] KeePass templates / KPEntryTemplates

Hi there. I wanted to reach out, I am the developer of KPET and hope to do a major revision on the plugin. My goal will be the keep all existing template code working BUT I want to offer users the ability to migrate to V2 on a per entry basis (that is my thinking right now, a right click option to upgrade an entry).

I want to move to properly using CustomData instead of advanced strings but also refine the way of defining UI fields to hopefully be more flexible/standardized. I put some thoughts together at the end of github.com/keepassxreboot/keepassxc/issues/8228

As you are one of the few apps that actually use the current format (not to mention the only Android KP app I think ive ever used) would love your input. If you have ideas in terms of where you think the format should go I would love to hear them, you are welcome to email me if you prefer my email is on my GH, rather than a GH issue.

Again, no plans to stop current format from working even with the new plugin version (whenever it comes out) but I think a migration option for users to something better would be a plus.

Start by reviewing the related discussion in keepassxreboot/keepassxc#8228 and the existing KPET template handling. No file, test, entry point, or concrete acceptance criteria are named; the migration scope and compatibility requirements would need to be decided before implementation could be considered done.