[19.0][MIG] website_appointment_booking: Migration to 19.0 - #10
Open
dnplkndll wants to merge 2 commits into
Open
[19.0][MIG] website_appointment_booking: Migration to 19.0#10dnplkndll wants to merge 2 commits into
dnplkndll wants to merge 2 commits into
Conversation
- _sql_constraints → models.Constraint class attribute (website_slug_unique).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Port of
website_appointment_bookingfrom 18.0 to 19.0.Depends on OCA#217 (resource_booking). This PR is branched off that PR's head (fork branch
19.0-mig-resource_booking), so the diff shows only the new module.Non-mechanical adaptations worth flagging
_sql_constraints→models.Constraintclass attribute (website_slug_unique).publicWidgetlegacy API (not OWL components), so the 19.0 OWLrecord.datam2o-object change does not apply; slot data is read from DOMdata-*attributes.data-in-monthis rendered as the string'1'/'0', so no boolean-t-attcoercion was needed.