51baba3eeb
refs CNVS-25916 the migration_tool plugin uses the secondary bundle override technique of having an extension bundle loaded in parallel. I don't think we want to support both that and the glue-module extension approach since only one plugin makes use of the former. In order to migrate that work to extend a core module, the work needs to be moved to a non-entry-point module (because overriding require names doesn't work if you're talking about the bundles rails knows how to load). All this patchset does is move the core work done in the content_migration bundle into it's own module to make a valid override target for the plugin refactor. Also adds this new module as a non-entry-point exception in the bundles.js, just like it's sibling file. TEST PLAN: 1) nothing should change on /courses/x/content_migrations Change-Id: I2dfa0d1b1d11657bb5931e8caae6ef9d4b3c9aec Reviewed-on: https://gerrit.instructure.com/70510 Reviewed-by: Simon Williams <simon@instructure.com> Tested-by: Jenkins QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Ethan Vizitei <evizitei@instructure.com> |
||
|---|---|---|
| .. | ||
| coffeescripts | ||
| controllers | ||
| helpers | ||
| jsx | ||
| messages | ||
| middleware | ||
| models | ||
| observers | ||
| presenters | ||
| serializers | ||
| stylesheets | ||
| views | ||