xmo-odoo

Do you already have a vision for a new API?

Ah so more something closer to upstream ammonia's behaviour?

@robodoo override=ci/security

For what it's worth, I think one of the issues is the ability to configure defaults for a plugin which is not required. `xdist` is a notable example of that...

I think there's already a PR for that: https://github.com/odoo/odoo/pull/177782

That would be really cool as combined with [nested language metavariable-pattern](https://semgrep.dev/docs/writing-rules/rule-syntax#metavariable-pattern-with-nested-language) it would allow better analysis of the combination of the host and the SQL content.

> However, if `f("string--")` and `f("--string")` are not matching, then either the documentation is **wrong** and should be updated or metavariable-regex must be correctly implemented according to the spec/doc. Regex-metavariable...

Bump, either behaviour is ok but the documentation really should be fixed, currently the `metavariable-regex` goes out of its way to state that matching is unanchored and anchoring needs to...

Also looks like it was fixed once in the past (#5458) after a similar report (#4807)

moc note: technically merge queues / trains and batches are not incompatible, you kinda just queue batches. So you could have queues of batches n > 1.