- 04 Apr, 2017 29 commits
-
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
The only reason the exclusion of require_once was not exploding before is because the call to provider_event_action() was being triggered first which required the file. We can't rely on this happening all the time. The doc update describes when the usage of is_event_visible() is appropriate. Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
The filter parameter was being passed in as the wrong argument which was allowing non action events to be returned. Part of MDL-55611 epic.
-
It was renamed to \core_calendar::event
-
Change to image_url because these are not "pix icons".
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
This test was dependant on the randomly generated group names coming back in a specific order. Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
The new implementation of calendar_get_events (i.e., \core_calendar\api::get_events) has a subtly different behaviour. So we need to maintain the existing implementation in deprecatedlib. Part of MDL-55611 epic.
-
Some unit tests needed to be updated to specify a few extra bits and pieces on the events to work properly with the new event vault behaviour. Part of MDL-55611 epic.
-
The logic from get_events has now been moved in to our local API and is used by the event vault to retrieve events, instead of querying the database directly. This has the advantage that it deals with overrides and only returns events for the relevant user. Part of MDL-55611 epic.
-
The event factory should simply instantiate an event for non action events and pass only action events through the plumbing. This way modules implementing the callbacks can be sure that what is passed in to the callback is actually supposed to be an action event. Part of MDL-55611 epic.
-
Our API infrastructure currently only deals with events created by course modules. Site, user, etc events can't be dealt with. Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Initially we were only sending "top level" events through our API i.e., events that can be repeated, but are not repeats themselves. In the future we will be sending ALL events through our API and int that situation the ID of the collection needs a small bit of logic to correctly set the ID of the parent. Part of MDL-55611 epic.
-
- 03 Apr, 2017 11 commits
-
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Do not display completion related events if completion is disabled. Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-
Part of MDL-55611 epic.
-