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

[18.0] [MIG] sale_cancel_reason: Migration to 18.0 #3506

Merged
merged 80 commits into from
Jan 28, 2025

Conversation

bizzappdev
Copy link
Contributor

No description provided.

guewen and others added 30 commits December 17, 2024 16:35

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
(../trunk-generic/ rev 29.1.1)
(../trunk-generic/ rev 32.1.1)
In order to get visibility on https://www.odoo.com/apps the OCA board has
decided to add the OCA as author of all the addons maintained as part of the
association.
* [MIG] sale_cancel_reason Migration to 10.0

* Follow coding standard

* Convert test to unittest2
Updated by Actualizar ficheiros PO com o novo POT (msgmerge) hook in Weblate.
Currently translated at 100.0% (23 of 23 strings)

Translation: sale-workflow-10.0/sale-workflow-10.0-sale_cancel_reason
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-10-0/sale-workflow-10-0-sale_cancel_reason/pt/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-12.0/sale-workflow-12.0-sale_cancel_reason
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-12-0/sale-workflow-12-0-sale_cancel_reason/
@bizzappdev bizzappdev marked this pull request as ready for review December 19, 2024 11:59
Copy link
Contributor

@jbaudoux jbaudoux left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

@rconjour rconjour left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Member

@bealdav bealdav left a comment

Choose a reason for hiding this comment

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

LGTM, thanks

<field name="model">sale.order</field>
<field name="inherit_id" ref="sale.view_order_form" />
<field name="arch" type="xml">
<xpath expr="/form/sheet/div/h1" position="after">
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure I understand properly, but in v17, the field is also not editable. And Look position and behaviour are exactly the same as in v17. PFA v17 and v18 screenshots.
V18
v18_SS

v17
v17-SS

@bealdav
Copy link
Member

bealdav commented Jan 17, 2025

Yes, I guess a migration with the same functionality as the previous feature is enough for now.
@rjaraspearhead, you could add a new feature in a new PR, right?
I propose to merge like that?

Thanks a lot.

Copy link

@rjaraspearhead rjaraspearhead left a comment

Choose a reason for hiding this comment

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

LGTM, thanks

Copy link
Contributor

@celm1990 celm1990 left a comment

Choose a reason for hiding this comment

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

Please squash administrative commits according this guide
https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests

Copy link
Contributor

@celm1990 celm1990 left a comment

Choose a reason for hiding this comment

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

Tested, LGTM, just a minor changes

sale order.
</p>
<group>
<field name="reason_id" widget="selection" />
Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer this approach instead of using the selection widget. Could you update it? This is better for the UI and allows users to search within the records.

Suggested change
<field name="reason_id" widget="selection" />
<field name="reason_id" options="{'no_create': True, 'no_open': True}" />

Copy link
Contributor

Choose a reason for hiding this comment

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

sounds a good improvement indeed

<field name="arch" type="xml">
<footer position="before">
<group>
<field name="reason_id" widget="selection" />
Copy link
Contributor

Choose a reason for hiding this comment

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

the same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changes are Done.

@bealdav
Copy link
Member

bealdav commented Jan 20, 2025

@bizzappdev do you think it is possible to update this PR as requested by @celm1990 or do you think it is inappropriate? Thanks

@bizzappdev bizzappdev force-pushed the 18.0-mig-sale_cancel_reason-BAD branch from fe734e7 to 458def4 Compare January 20, 2025 14:22
@bealdav
Copy link
Member

bealdav commented Jan 22, 2025

Thanks @bizzappdev

@celm1990 could you approve ?

Copy link

@marcelofrare marcelofrare left a comment

Choose a reason for hiding this comment

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

LGTM functionally

Copy link
Contributor

@celm1990 celm1990 left a comment

Choose a reason for hiding this comment

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

LGTM
@OCA/crm-sales-marketing-maintainers could somebody please review this? , thanks a lot!

@simahawk
Copy link
Contributor

/ocabot migration sale_cancel_reason
/ocabot merge nobump

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Jan 28, 2025
@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 18.0-ocabot-merge-pr-3506-by-simahawk-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot mentioned this pull request Jan 28, 2025
61 tasks
@OCA-git-bot OCA-git-bot merged commit 7f9dc2d into OCA:18.0 Jan 28, 2025
6 of 7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at a254aba. 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.