OCA / margin-analysis

Odoo Financial Controlling (margin, costs, ...)
https://odoo-community.org/project/9
GNU Affero General Public License v3.0
74 stars 161 forks source link

[12.0][FIX] product_pricelist_margin : change dependency #135

Closed legalsylvain closed 1 year ago

legalsylvain commented 2 years ago

following @pedrobaeza : I checked and installed the module. product_pricelist_margin. changing the dependency from 'sale' to 'account' is working. (https://github.com/OCA/product-attribute/pull/1101#issuecomment-1176251703)

pedrobaeza commented 2 years ago

But I want a pure product dependency, which is possible for only getting the price. Why do you need account?

legalsylvain commented 2 years ago

Account is required for computing the Margin. (Compute-all function)

I'm curious, in witch case do you use pricelist without account installed ?

pedrobaeza commented 2 years ago

It's not a real case right now, but to reduce the dependencies to minimum, the same as Odoo does with the pricelists being bundled in product module, not sale nor account. What about putting in 13.0 our module as is (we keep your commit history and attribution though) and mount on top of it this extension for margin?

legalsylvain commented 2 years ago

What about putting in 13.0 our module as is (we keep your commit history)

I don't understand how it can be "your module", but "my history". But maybe I missed something...

It's not a real case right now, but to reduce the dependencies to minimum

Well, I think it will be allways a theoritical case. (using pricelist without account, because pricelist is used in website_sale, sale and point_of_sale, that all depends (of course) of account), so arguing theoritical case that can not occures is maybe not a valid argument ?).

We have two options : 1) one single module with margin and all the stuff. (= port current OCA product_pricelist_margin in V13, adapting with your remarks)
2) two modules, one with price feature, and another glue module with margin.

I think having 2 modules :

So, that giving said, I don't make it a casus belli.

Let me know.

pedrobaeza commented 2 years ago

I take your commit history, rewriting the module name, and then just add a new commit with the changes to make it work according new scheme for 13.0.

legalsylvain commented 2 years ago

OK. (Maybe you didn't saw my previous edited comment)

But If I reword your proposal :

even if it requires a bit more work than keeping a single module, I can live with it, and if it allows the OCA community to make more use of the simulation module developed by GRAP, that's great in the long run.

Let me know if all is OK for you.

pedrobaeza commented 2 years ago

Great, thanks for arriving to a deal. We'll do in the following days.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this pull request in the past 4 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 PR to never become stale, please ask a PSC member to apply the "no stale" label.