-
-
Notifications
You must be signed in to change notification settings - Fork 675
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
[12.0][MIG] resource_multi_week_calendar #1389
base: 12.0
Are you sure you want to change the base?
[12.0][MIG] resource_multi_week_calendar #1389
Conversation
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
…calendar This is the bones of the implementation. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
…atch This is the real implementation work. With this method implemented, all other methods correctly get the correct week each time. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
The epoch date is hidden on the child anyway. Let's just hide it, and always make sure to get the parent's epoch date. This gets rid of the complicated computation stuff that won't backport well to v12. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
…s attendances The idea here is that the children contain all the logic/attendances, and the parent is just a holder of children. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
@huguesdk Backport done. |
05e4d5e
to
698f076
Compare
I need this elsewhere. It _technically_ reduces performance by doing the same calculation twice, but this module is horrible as pertains to performance in any case. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
698f076
to
50f0b0c
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.
unfinished review done with @huguesdk
- `parent_calendar_id` is now `ondelete="cascade"`. - Renamed `family_calendar_ids` to `multi_week_calendar_ids`. - Renamed `current_calendar_id` to `current_multi_week_calendar_id`. - Renamed `_get_calendar` to `_get_multi_week_calendar`. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
- Improved the comment on how week_sequence works. - Renamed family_size to calendar_count - Added a comment on _get_multi_week_calendar() returning a 1-item recordset. - Re-optimised the current week calculation. Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
6766eea
to
098a235
Compare
Review with @huguesdk finished, all things addressed. |
098a235
to
c7a15cf
Compare
…ndar Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
c7a15cf
to
1d4db07
Compare
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
A backport of #1384
Internal task: T12626