-
-
Notifications
You must be signed in to change notification settings - Fork 873
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
9.0 [MIG] port partner_firstname #232
Conversation
In the base module, a SQL constraint check that one is filled with the name of the partner. With this module, the name field is filled after creating so we have to remove. A python constraint checks that one is the firstname or lastname field filled.
@@ -23,6 +23,7 @@ addon | version | summary | |||
[partner_contact_gender](partner_contact_gender/) | 9.0.1.1.0 | Add gender field to contacts | |||
[partner_contact_in_several_companies](partner_contact_in_several_companies/) | 9.0.1.0.0 | Allow to have one contact in several partners | |||
[partner_contact_nationality](partner_contact_nationality/) | 9.0.1.0.0 | Add nationality field to contacts | |||
[partner_firstname](partner_firstname/) | 9.0.2.0.0 | Split first name and last name for non company partners |
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.
This is not needed, the bot will update it automatically
Only thing which I see is missing in my PR is the new check for empty address for non contact addresses. Otherwise I feel there is more things in my PR than in yours (Updated contributor list, licenses, hide . So do you mind if I take my PR #238 as the basis to include your change to test the constraint on non contact addresses ? |
In fact there is now 3 PR with #215 |
No description provided.