xmo-odoo

Why? I already approved the PR.

Shouldn't that be whoever's in charge of bugfix? I've no idea what the team flow is.

> Yes, the `upgrade` code should be adapted to change all the `import` before this is merged. I was mostly asking to see if we could just move the import...

Turns out moving the `UpgradeHook` is not feasible without adding back at least some infrastructure (see odoo/upgrade#4328), and the very limited improvements left when that's removed aren't really worth it....

> but instead counts the number of problems per file and per rule That means it can't flag an issue being moved around, or code being rewritten but reintroducing the...

> As for the "moving" part, I think it's not a good thing to do things based on the line number. For instance, if I'm working on a file and...

> I like the conflict-less parts, but I went for a single file, because it makes it easy to have an overview of the suppressed errors (which rules are suppressed,...

> With `ember-template-lint`'s approach, I might see 10 removed files and +/- 10 added files, and I'm going to need to dig into all of those to see whether things...

> Truncating the constraint name does not guarantee uniqueness of those names in Postgres. Maybe we should do it like in #100736. Indeed but I was not trying to fix...

@robodoo retry