Empirical Core is the mono repo for the Quill.org codebase. This repo contains both the Quill Learning Tools, such as Quill Connect, and the Quill Learning Management System, the platform that enables teachers to provide assignments and view results. (Empirical is the name of the nonprofit building Quill.org).
Part two of the trial runner -- I've decided to split this up yet again because this section required a refactor of some of our existing components, which are now shared. The big change here is that we're no longer reloading the page, but setting the results of new get methods when guidelines and dataset_relevant_texts are updated into the parent components, and invalidating the caches in the background. window.reload isn't a big deal on largely static pages, but since the trial runner is essentially one big form, I didn't want to risk users losing information they'd already input if they are making changes in one of these areas.
WHY
This is a requisite part of the work for the trial runner.
HOW
Add various fields to the trial runner, and repurpose existing components for this page as well. This involved some backend work to add and test new index functions for the relevant controllers.
Tested the new flows, including that updating guidelines and dataset relevant texts on one page correctly updates them on the other. Jamie will QA when this card is complete.
PR Checklist
Your Answer
Have you added and/or updated tests?
YES
Have you deployed to Staging?
Tested locally, will deploy when the rest of the page is in place.
Self-Review: Have you done an initial self-review of the code below on Github?
WHAT
Part two of the trial runner -- I've decided to split this up yet again because this section required a refactor of some of our existing components, which are now shared. The big change here is that we're no longer reloading the page, but setting the results of new
getmethods when guidelines and dataset_relevant_texts are updated into the parent components, and invalidating the caches in the background.window.reloadisn't a big deal on largely static pages, but since the trial runner is essentially one big form, I didn't want to risk users losing information they'd already input if they are making changes in one of these areas.WHY
This is a requisite part of the work for the trial runner.
HOW
Add various fields to the trial runner, and repurpose existing components for this page as well. This involved some backend work to add and test new index functions for the relevant controllers.
Screenshots
Notion Card Links
https://www.notion.so/quill/Trial-Runner-Page-12ed42e6f9418002b2f0e2e7917a8117?pvs=4
What have you done to QA this feature?
Tested the new flows, including that updating guidelines and dataset relevant texts on one page correctly updates them on the other. Jamie will QA when this card is complete.