Closed jjscarafia closed 9 months ago
Yes, I also see weird to require a module to do this.
I also see it weird. But to be honest we've been using this to migate modules and it's awesome. It fix all the views. For me, no problems not to merge it. I don´t see any nicier not so difficult solution.
If you prefer, we can close the pr.
We create it because we believe it could help a lot to migrate modules.
The approach is not nice but it works.
A dedicated hosted repository looks good to me, but I feel that it could be too much. For now it's just for this module, this use case of migration between 16 and 17.
Thanks you both!
But why the same algorithm can't be done with regular Python code as the rest of the module migrator does?
Hi @pedrobaeza We've started doing so but it was taking more time that the one available on our side. There are some challengues as:
Yeah, I see. I understand if the work is very huge and you don't want to continue. The problem is that this library wants to be independent from Odoo and light, so doing that way will compromise the foundation principles. A new repo or server-tools module can be added though.
thanks @pedrobaeza So proposing this module on server-tools for v17 seems a good one? If I'm not wrong, the mdoule can be uninstallble and still be loaded for the patch. So with a good readme it will not break anything.
Yeah, I think so.
Hey @pedrobaeza @jjscarafia, here it is the new PR https://github.com/OCA/server-tools/pull/2775, it perfectly works with the module uninstallable=False.. I think we can go ahead, merge it and close this one.
@pedrobaeza what do you think about this?
Making this script a commont script inside the tool was to heavy. We've created a new folder "addons" and a new module to help on views migration on 17.
We've been using it and is working like a charm.
Simply:
odoo -i [module_name] -d [database_name] --load=base,web,views_migration_17