-
-
Notifications
You must be signed in to change notification settings - Fork 821
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
[13.0][MIG] partner_priority #870
Conversation
This module adds a priority field to contacts which can be configured within the configuration menu. [UPD] LINT errors fixed lint error, renamed test py file, added missing readme [UPD] Removed unused file removed incorrect py file [FIX] wrong sequence val in test Remove Test [FIX] Data File Sequence Fixed wrong sequence field name on data file. [UPD] noupdate Removed <data> element and moved noupdate into Odoo as suggested by reviewers. [UPD] Reviewer Changes Changes based on reviewer's suggestions [UPD] Additional Review Changes Additional changes requested from reviewers [UPD] Sequence Moved next sequence out of create method and into field def. [UPD] Review Change [FIX] LINT
Hi @patrickrwilson, |
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.
Functional test 👍
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
@Saran440 @ps-tubtim Could you review this ? |
This PR has the |
|
||
name = fields.Char(string="Priority", required=True) | ||
description = fields.Text(required=True) | ||
sequence = fields.Integer( |
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.
Having this field set from an ir.sequence instance looks a little bit to over-engineering to me.
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 remarks. But not blocking as this is a migration.
737cadc
to
7a6947d
Compare
/ocabot merge |
Hi @NL66278. Your command failed:
Ocabot commands
More information
|
/ocabot merge nobump |
On my way to merge this fine PR! |
Congratulations, your PR was merged at 9f4aa72. Thanks a lot for contributing to OCA. ❤️ |
@NL66278 The ocabot merge command has changed. The nobump option does not generate wheels for pypi. Even for migration PRs now, use major/minor/patch. |
@rousseldenis In the past when I used major on a migration merge, I was told to leave out the major/minor/patch altogether. Recently the version argument became required, but the nobump was added, so I used that. So what am I supposed to use on a migration merge? major would seem to me the most logical... |
Following the conversation in mailing list, the idea is to use patch. So, at the end, the module would have 13.0.1.0.1. But the wheels should be generated. |
Ready for review.