vfe-odoo
vfe-odoo
@robodoo r+ rebase-ff
@robodoo r+
Tip: put the PR in draft before retargeting to avoid pinging all codeowners ;)
> I didn't investigate why but many of your `meth` refs are broken. cause he's referencing `odoo.models.BaseModel.method` when we're autodocumenting `odoo.models.Model.method` in the "ORM API" file ^^'
> @odoo/doc-review When you have a moment can you review this change? When a PR is ready for review, just hit the "Ready for review" button and the responsible teams...
It's better if it's clean directly, but was faster for us here to directly fix it without requesting/doing a force-push only to update the commit :). Thanks :+1:
Moved to #101304
Please mark a PR as "Ready for Review" only when it went through Testing process (Testing IN, Validation BE and Testing BE) to notify codeowners only on the final version...
@smetl Can I have your thoughts on this problem ? This fix goes a bit too wild imho, it's kind of strange we have to post invoices one by one...
And what about CRONs ? :thinking: Is it expected/a problem when invoices are generated with the superuser tz ?