search

shopinvader / odoo-shopinvader

Odoo Modules. Sorry Magento, Shopinvader is coming
GNU Affero General Public License v3.0
121 stars 104 forks source link

RFC Services' work context partner should be shopinvader.partner #787

Closed simahawk closed 1 year ago

simahawk commented 4 years ago

The partner in the context should always be the binding (shopinvader.partner) and not the real partner (res.partner). A partner in the context of shopinvader, must always have a binding otherwise is not even found (except for addresses). As per products, we often attach information to bindings because they are peculiar to a specific shop/backend. This would ease lookup of bindings (we don't have to filter every time by backend when needed) and their custom data and some sort of isolation between backends. OTOH is always easy to get the real partner from the partner via record_id.

CC @sebastienbeau @lmignon

lmignon commented 4 years ago

@simahawk That makes sens for me.

simahawk commented 3 years ago

1st step has been done here https://github.com/shopinvader/odoo-shopinvader/pull/817 invader_partner is set by the controller in the work context. Next would be to make all services rely on it where it makes more sense.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.