-
-
Notifications
You must be signed in to change notification settings - Fork 851
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
[16.0] Replace partner_address_two_lines by partner_display_name_line_break #1546
[16.0] Replace partner_address_two_lines by partner_display_name_line_break #1546
Conversation
1a5bd58
to
1ecd936
Compare
1ecd936
to
5f14134
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.
For the test, please focus on writing a "unit" test by calling name_get
on different partners structures. We just want to make sure we get a \n
instead of a ,
and that we don't get the separator and the contact type in case there's no contact name.
5f14134
to
beba215
Compare
7999f3b
to
eff6598
Compare
eff6598
to
a137b89
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.
would be nice to have a screenshot or smth…
LG tough.
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.
@rousseldenis which name in your head? |
name = self.child_partner_name.with_context( | ||
_two_lines_partner_address=True | ||
)._get_name() | ||
self.assertEqual(name, "Test Company Name\n Test Partner Name") |
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.
Leave out the blank after \n
. Same goes for the invoice address.
The improved code does not add a space at the beginning of the second line, which in my opinion is correct. The old code did however.
Hi @rafaelbn, do you still want to rename the module I am migrating it to 17.0. I can rename it as a part of the migration |
@NL66278 @JuMiSanAr is this still need fixing PR? Any idea with module name @hbrunn ? partner_display_name_break_line ? Thank you! 😄 Remember @trisdoan , this PR depends in a Odoo/odoo PR too |
/ocabot rebase |
@rafaelbn The rebase process failed, because command
|
@rafaelbn My comment on how to fix the failing test has not been taken up after half a year. The prerequisite Odoo PR has a merge conflict that is also not resolved. If nothing is done on these issues I would propose closing the PR. |
Test updated. Regarding the module name, I'm open to suggestions. |
@NL66278 right! Test are fixed now! 🥳 |
@JuMiSanAr I have two more request for approval and merge:
Nearly the same as the module name proposed by @rafaelbn , but I think "line break" is the recognized term for this. |
I agree
El mié, 24 abr 2024, 10:14, Ronald Portier ***@***.***>
escribió:
… @JuMiSanAr <https://github.com/JuMiSanAr> I have two more request for
approval and merge:
- Squash your commits, so we are left with one commit;
- Rename the module to partner_display_name_line_break;
Nearly the same as the module name proposed by @rafaelbn
<https://github.com/rafaelbn> , but I think "line break" is the
recognized term for this.
—
Reply to this email directly, view it on GitHub
<#1546 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCU63ZGTW2AKKQ6CZLDBP3Y65SV5AVCNFSM6AAAAAAZP5V3Z6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGM2TAMJZHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
675e239
to
7a536e8
Compare
7a536e8
to
b111a99
Compare
b111a99
to
9e43456
Compare
There you go |
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. Thanks for your contribution. Two questions, not breaking::
- Why the dependency on context key? If this module is installed, apparently the instance administrators want to display the name and the company on two lines.
- Does this really depend on the Odoo PR? If the Odoo PR is not accepted or merged, you will also get possibly the word 'Invoice' or one of the other type descriptions on a separate line. To me this seems to be consistent with the partner name on a second line.
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.
Thank you! 👍🏼
NL66278 approved these changes
👍 LGTM. Thanks for your contribution. Two questions, not breaking::
- Why the dependency on context key? If this module is installed, apparently the instance administrators want to display the name and the company on two lines.
- Does this really depend on the Odoo PR? If the Odoo PR is not accepted or merged, you will also get possibly the word 'Invoice' or one of the other type descriptions on a separate line. To me this seems to be consistent with the partner name on a second line.
Hello @@JuMiSanAr, LGTM. I agree with NL66278 that it does not need to depend on that PR |
/ocabot merge minor |
This PR looks fantastic, let's merge it! |
@NL66278 your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-1546-by-NL66278-bump-minor. 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. |
please also add a PR to https://github.com/OCA/OpenUpgrade/blob/16.0/openupgrade_scripts/apriori.py#L6 to document the renaming for openupgrade. /ocabot merge minor |
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at 1ccae3b. Thanks a lot for contributing to OCA. ❤️ |
Fix the separation in two lines, and add tests.
Depends on: odoo/odoo#126451