Closed rgachuhi closed 2 years ago
I am not sure how we handle these kinds of references other than inspecting each webcontent file to search for and replace these relative paths. Not sure how many webcontent files use standard file reference forms such as src, source etc. Could we simply defer handling these cases after course injection in torus? I.e. fix those activities that fail to work as part of package QA
Some of the supporting webcontent files have non-standard references with activities, especially custom activities. Those are currently being ignored by the course-digest. The PR resolves this by appending all other webcontent files to the media-manifest.json