PRs conflicts

[yelizariev]

Design of the tool doesn't fit well for contributing: if there are 5 pull request about the same migration (e.g 13 to 14) and all them target the same place of code, then merging one of them leads to conflicts in all others. Well, fixing a conflict not that difficult, but

• We need to wait when the author has time to do it
• Once it's done, another pull request may be merged, which means that the author has to fix conflict again
• You cannot use git-aggregate tool to apply your unmerged PRs

To resolve this, I would suggest to collect rules in separate files, rather than in a dictionary like _TEXT_ERRORS. It may have the following structure:

/migration_scripts/13_14/text_errors/some_name.json /migration_scripts/13_14/text_errors/another_name.json

[legalsylvain]

Hi @yelizariev that is a great idea. do you want to propose a PR ?

thanks !

[yelizariev]

Yes, I'll do it some day... I can potentially do it on top of https://github.com/OCA/odoo-module-migrator/pull/28 (and make it with less changed files https://github.com/OCA/odoo-module-migrator/pull/28#discussion_r509254275)

[yelizariev]

Done in #42

[rvalyi]