Basic QTI zip loading prototype.

[rtibbles]

Summary

• Ground work for QTI work
• Loads content from a QTI zip and then renders, inserting locally referenced files

References

…

Reviewer guidance

…

---

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[nucleogenesis]

I looked at this before but realized I never commented. I gave it another pass and everything looks good to me. This will be an excellent foundation to work from

[indirectlylit]

A little clarification

Suggested change

	return new URL(
	relativeHref,
	new URL(this.getFilePath(), 'http://b.b/')
	).pathname.substring(1);
	// iterative URL path construction using dummy domain
	return new URL(
	relativeHref,
	new URL(this.getFilePath(), 'http://example.com/')
	).pathname.substring(1);

[rtibbles]

I deliberately used a non-valid TLD to avoid any confusion, but yes.

[github-actions]

Build Artifacts