[16.0][REF] replace res.partner computes with inverse function in checkin.partner #353
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tion in checkin partner fields.
DarioLodeiros
approved these changes
Sep 21, 2025
Member
DarioLodeiros
left a comment
DarioLodeiros
left a comment
There was a problem hiding this comment.
Do the last two commits correspond to this PR?
Member
Author
|
Yes, for some reason, removing the computes in res.partner, makes the compute of services in reservation fail, and after fixing the reservation problem, the pms.room address compute fails |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until now, the checkin.partner fields that updated the related partner were done through a complex compute on the partner side with multiple depends. With this change, it becomes a simple inverse in checkin.partner.
The address related fields were not modified in this PR, it will be handled in a further PR who removes the residence address related fields.