Use a module/path mapping for RequireJS overrides instead of just paths.
Instead of attempting to derive the module portion of a RequireJS override strictly from the path to the JS file, we now use a dictionary where the module name must be explicitly specified. This allows us to compensate for files which do not follow a naming scheme that is compatible with RequireJS without having to normalize all files. This is extremely important when using third-party dependencies.
Showing
- common/djangoapps/pipeline_mako/__init__.py 3 additions, 3 deletionscommon/djangoapps/pipeline_mako/__init__.py
- common/djangoapps/pipeline_mako/tests/test_render.py 8 additions, 8 deletionscommon/djangoapps/pipeline_mako/tests/test_render.py
- lms/envs/common.py 8 additions, 8 deletionslms/envs/common.py
Loading
Please register or sign in to comment