-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[17.0][MIG] tracking_manager #2916
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
Conversation
6c077b4 to
cbfc38e
Compare
0719033 to
3928339
Compare
GuillemCForgeFlow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some suggestions, for the rest I have functionally tested and works fine 👍🏿
3928339 to
358c4fe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! functional and code review 👍🏿
thank you for accepting the suggestions btw 😄
you can already mark all discussions as resolved!
MohamedOsman7
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code & functional review LGTM
|
This PR has the |
|
@pedrobaeza could you merge this? |
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
|
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 17.0-ocabot-merge-pr-2916-by-pedrobaeza-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. |
|
/ocabot merge nobump |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
- remove tracking_model (less model, less code, less issue) - add automatic rule for default config (this avoid missing tracked field after module installation)
For example on the product if you open the 'stock.putaway.rule' you have activated the tracking on putaway_rule_ids change on rule should be posted on the related product
- track m2m simplify using native mail_thread and process them like text - simplify code for track one2many - avoid useless code on model not impacted by the tracking
Instead of complexe tracking throught the context just track change and process the message at the end using the precommit feature (the message are posted just before commiting)
Co-authored-by: Yoshi Tashiro (Quartile) <tashiro@quartile.co>
358c4fe to
c906b35
Compare
|
@pedrobaeza rebased and fixed. |
|
/ocabot merge nobump |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
Congratulations, your PR was merged at d2cdf00. Thanks a lot for contributing to OCA. ❤️ |
No description provided.