-
Bug
-
Resolution: Fixed
-
Minor
-
4.0.7
-
MOODLE_400_STABLE
-
MOODLE_400_STABLE, MOODLE_401_STABLE, MOODLE_402_STABLE
-
MDL-77858-401 -
As reported in MDL-75316:
displayException isn't a valid import name. We're importing that, but it's not an export in Notification. We need to import exception and alias that if we want to call it displayException.
E.g.
import {exception as displayException, addNotification} from 'core/notification';
It looks like we've already introduced the same problem in core in 2 other places, so I'm going to suggest please creating an issue to fix those too.
- https://github.com/moodle/moodle/blob/fba0658777a10d553076c815a7f6a336ff0bbdb9/calendar/amd/src/manage_subscriptions.js#L29
- https://github.com/moodle/moodle/blob/fba0658777a10d553076c815a7f6a336ff0bbdb9/lib/editor/tiny/plugins/equation/amd/src/ui.js#L30
Kind of similar to MDL-76491 (also about invalid imports from core/notification)
- Discovered while testing
-
MDL-75316 (PARENT) Implement LMS foundation for sharing content to MoodleNet (share activities)
- Closed
- has a non-specific relationship to
-
MDL-76491 ESlint rules are not catching undefined use of Notification module
- Closed
- is duplicated by
-
MDL-77881 Javascript: Invalid displayException import
- Closed