Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MIG][16.0] product_abc_classification #1192

Merged
merged 21 commits into from
Sep 18, 2023

Conversation

rousseldenis
Copy link
Sponsor Contributor

@rousseldenis rousseldenis commented Nov 10, 2022

Forwardported:

As this is a base module that is intended to be extended by adding profile types to ABC Classification profiles (and corresponding logic), this cannot be tested as is.

You should try this : #1196

@rousseldenis
Copy link
Sponsor Contributor Author

rousseldenis commented Nov 10, 2022

@MiquelRForgeFlow I didn't succeded in getting 13.0 and then applying our changes (too much conflicts).

I'll try to identify what can be imported from your version

@rousseldenis
Copy link
Sponsor Contributor Author

/ocabot migration product_abc_classification_base

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Nov 10, 2022
@OCA-git-bot OCA-git-bot mentioned this pull request Nov 10, 2022
55 tasks
@rousseldenis rousseldenis force-pushed the 16.0-mig-product_abc_classification-dro branch from 717381f to 7d9031f Compare November 10, 2022 12:43
@rousseldenis rousseldenis changed the title [MIG][16.0] product_abc_classification_base [MIG][16.0] product_abc_classification Nov 10, 2022
Then the cron classification will proceed to assign to these products one of the profile's levels.

NOTE: If you profile (or unprofile) a product category, then all its
child categories and products will be profiled (or unprofiled).
Copy link
Contributor

@legalsylvain legalsylvain Nov 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi. I don't see this feature in the code. (I was expecting an inheritance of product.category model) Did I missed something ?
Naive question because I don't use this module for the time being.

Copy link
Sponsor Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@legalsylvain Thanks for this. This is WIP for now, some refactoring before the end of the day :-)

Copy link
Sponsor Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lmignon Do we agree that with multi level on products, setting the levels on category would be harsh to implement ?

What was done before :

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@legalsylvain Thanks for this. This is WIP for now, some refactoring before the end of the day :-)

No problem !
Note : you can use "Draft PR" if it's WIP.

Copy link
Sponsor Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@legalsylvain Yes I know, I usually use it when process would last a long time. Here, I knew this would be ready fast

@rousseldenis
Copy link
Sponsor Contributor Author

/ocabot migration product_abc_classification

Copy link
Sponsor Contributor

@lmignon lmignon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @rousseldenis. LGTM (Code + Functional tests with #1196 )

@rousseldenis rousseldenis force-pushed the 16.0-mig-product_abc_classification-dro branch 2 times, most recently from 1a0ea49 to cc97df9 Compare November 22, 2022 12:22
@chienandalu
Copy link
Member

@MiquelRForgeFlow I didn't succeded in getting 13.0 and then applying our changes (too much conflicts).
I'll try to identify what can be imported from your version

@rousseldenis What's your roadmap in this regard? As I see from the commit history, right the v13.0 code is just discarded in favour of the one coming from v10.0

@rousseldenis
Copy link
Sponsor Contributor Author

rousseldenis commented Jan 11, 2023

@MiquelRForgeFlow I didn't succeded in getting 13.0 and then applying our changes (too much conflicts).
I'll try to identify what can be imported from your version

@rousseldenis What's your roadmap in this regard? As I see from the commit history, right the v13.0 code is just discarded in favour of the one coming from v10.0

Indeed as the rebasing was a nightmare.

This approach has been improved in some production environments, the essential difference is the multi relationship between products and profiles/levels.

As the commits introduced in v13 have no sense with this approach, I haven't taken them apart an improvement on view level by @MiquelRForgeFlow (see PR comment)

Copy link
Contributor

@sbejaoui sbejaoui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, code review

@rousseldenis
Copy link
Sponsor Contributor Author

I will add tabs as extending the module like in :

OCA/stock-logistics-reporting#257

image

introduce some complexity in the form view.

@rousseldenis
Copy link
Sponsor Contributor Author

With sale_stock module installed:

image

@lmignon lmignon force-pushed the 16.0-mig-product_abc_classification-dro branch 3 times, most recently from d804a71 to 6403c05 Compare April 5, 2023 14:53
@rousseldenis rousseldenis force-pushed the 16.0-mig-product_abc_classification-dro branch from 6403c05 to 81726cf Compare September 15, 2023 13:55
@rousseldenis
Copy link
Sponsor Contributor Author

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-1192-by-rousseldenis-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Sep 18, 2023
Signed-off-by rousseldenis
@OCA-git-bot
Copy link
Contributor

@rousseldenis your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-1192-by-rousseldenis-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@rousseldenis rousseldenis force-pushed the 16.0-mig-product_abc_classification-dro branch from 648cf39 to 70beefc Compare September 18, 2023 09:56
@rousseldenis
Copy link
Sponsor Contributor Author

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 16.0-ocabot-merge-pr-1192-by-rousseldenis-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 1e5f957 into OCA:16.0 Sep 18, 2023
9 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 6e29ef8. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants