Skip to content

issue#45: trigger course_module_updated on dates update#50

Open
dmitriim wants to merge 1 commit intomoodleou:mainfrom
catalyst:issue45
Open

issue#45: trigger course_module_updated on dates update#50
dmitriim wants to merge 1 commit intomoodleou:mainfrom
catalyst:issue45

Conversation

@dmitriim
Copy link

@dmitriim dmitriim commented Dec 12, 2022

This pull request adds triggering \core\event\course_module_updated event after updating a date for a specific activity.
This is required as technically activity is getting updated when dates get changed.

* @param \block_base $block the block to save the dates for.
* @param array $dates a list of new dates.
*/
final public function save_new_dates(block_base $block, array $dates) {
Copy link
Author

Choose a reason for hiding this comment

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

There is no real reason to do have this new method for for the block instance. It's done for consistency.

Choose a reason for hiding this comment

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

I'm not too sure what you mean by consistence here. Consistency with what?

Copy link
Author

Choose a reason for hiding this comment

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

So we added save_new_dates method to modules related class, hence I'd like to keep it consistent for blocks as well. But technically there is no reason to do so as we don't trigger anything for the blocks.

Copy link
Member

Choose a reason for hiding this comment

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

If even Cameron does not understand what is giong on here, then you need to improve the comment (instead of answering in github comment which will neve be seen again.)

You also need to write your pull request to explain what you are doing and why. Yiou may konw, but I am not telepathic.

Copy link
Author

@dmitriim dmitriim Jan 23, 2023

Choose a reason for hiding this comment

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

I have updated a pull request description to explain what's happening in the code. As well as added comment to explain a new method a little bit more. Please have a look and let me know if that's better now.

@cameron1729
Copy link

Thanks @dmitriim - the code here seems reasonable to me. Just one small comment to address but it's minor - and actually after looking a bit longer I'm pretty sure I understand what was meant by consistency.

@Syxton Syxton mentioned this pull request Jul 2, 2025
dvdcastro added a commit to lsuonline/moodle-report_editdates that referenced this pull request Mar 11, 2026
…u#50)

Add final save_new_dates() wrapper method to both base extractor classes:
- report_editdates_mod_date_extractor: calls save_dates() then triggers
  \core\event\course_module_updated so calendar and other observers react
- report_editdates_block_date_extractor: calls save_dates() for consistent API

Update index.php to call save_new_dates() instead of save_dates() for
both module and block date updates.

Ref: moodleou#50 (commit bb1f9b3)
Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants