Skip to content

[19.0][MIG] contract_membership_delegated_partner: Migration to 19.0 - #228

Merged
OCA-git-bot merged 16 commits into
OCA:19.0from
Tecnativa:19.0-mig-contract_membership_delegated_partner
Jul 23, 2026
Merged

[19.0][MIG] contract_membership_delegated_partner: Migration to 19.0#228
OCA-git-bot merged 16 commits into
OCA:19.0from
Tecnativa:19.0-mig-contract_membership_delegated_partner

Conversation

@victoralmau

@victoralmau victoralmau commented Jul 1, 2026

Copy link
Copy Markdown
Member

Migration to 19.0

Locked by:

Please @pilarvargas-tecnativa and @eduezerouali-tecnativa can you review it?

@Tecnativa TT63400

@OCA-git-bot OCA-git-bot added series:19.0 mod:contract_membership_delegated_partner Module contract_membership_delegated_partner labels Jul 1, 2026
chienandalu and others added 16 commits July 23, 2026 16:01
- Adaptation to the new OCA contract module paradigm.
Update "development_status": "Production/Stable"
[UPD] Update contract_membership_delegated_partner.pot

[BOT] post-merge updates
…elds are always truthy

This is an additional sanity check to make sure that fields that are
expected to be available are actually available.

The situation here is a little tricky. Especially as pertains date_from
and date_to; these fields are `required=True` nowhere. Not on the
product, not on the membership invoice, and not on the membership line.
However, they _are_ set as required in the product and membership line
views. If these values are ever empty, it's a sure sign that something
went wrong somewhere, because the user should not be able to reach such
a state via the UI.

One sure way to reach that state was via the demo data, however, which
had no start and end dates. This is now fixed.

The situation for the variable period fields is similar. These fields
should never be empty when the membership type is variable, and it's not
typically possible to empty these values via the UI. For convenience's
sake, I simply set them to required an sich, with a default value.

Signed-off-by: Carmen Bianca BAKKER <carmen@carmenbianca.eu>

[BOT] post-merge updates
TT51523

[UPD] Update contract_membership_delegated_partner.pot

[BOT] post-merge updates
[UPD] Update contract_membership_delegated_partner.pot

[BOT] post-merge updates
@victoralmau
victoralmau force-pushed the 19.0-mig-contract_membership_delegated_partner branch from 9f20117 to fdca242 Compare July 23, 2026 14:01
@pedrobaeza

Copy link
Copy Markdown
Member

/ocabot migration contract_membership_delegated_partner

@OCA-git-bot OCA-git-bot added this to the 19.0 milestone Jul 23, 2026
@OCA-git-bot OCA-git-bot mentioned this pull request Jul 23, 2026
11 tasks
@pedrobaeza
pedrobaeza removed the request for review from pilarvargas-tecnativa July 23, 2026 14:26
@pedrobaeza

Copy link
Copy Markdown
Member

/ocabot merge nobump

@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 19.0-ocabot-merge-pr-228-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot
OCA-git-bot merged commit 8ffcc9a into OCA:19.0 Jul 23, 2026
7 checks passed
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at ac5ca40. Thanks a lot for contributing to OCA. ❤️

@pedrobaeza
pedrobaeza deleted the 19.0-mig-contract_membership_delegated_partner branch July 23, 2026 14:34
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.

9 participants