-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #6962: Remove jinja interaction templates and integrate css file into webpack #7286
Fix #6962: Remove jinja interaction templates and integrate css file into webpack #7286
Conversation
@Jamesjay4199, ptal at the frontend tests, they are failing. |
Codecov Report
@@ Coverage Diff @@
## develop #7286 +/- ##
==========================================
+ Coverage 89.4% 98.8% +9.39%
==========================================
Files 1208 381 -827
Lines 98111 64554 -33557
Branches 2637 0 -2637
==========================================
- Hits 87719 63781 -23938
+ Misses 9755 773 -8982
+ Partials 637 0 -637
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## develop #7286 +/- ##
===========================================
- Coverage 82.54% 82.53% -0.01%
===========================================
Files 1042 1042
Lines 57560 57558 -2
Branches 2643 2643
===========================================
- Hits 47511 47505 -6
- Misses 9407 9411 +4
Partials 642 642
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! One comment.
…tion-template-removal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just want to confirm that practice sessions and review tests were manually tested as well?
Yes @seanlip, I created an exploration with multiple choice and I played it without any change in style.
@vinitamurthi, the interaction that got affected in review_test and practice_session is the multiple-choice input and I tested it while testing the exploration editor and player and it worked fine. |
PTAL @nithusha21, @aks681 as code owner. thanks |
@Jamesjay4199 Did you try creating 'questions' in the topic and skill editors? |
No I did not. |
I don't think that is enough. You would need to manually try every single one of the interactions as you have touched all those files. (The easiest, in dev env, is probably to load all_interactions exploration, and view it in both explore/ and create/ views). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving as I am going to be out this weekend and don't want this to block you. Once you confirm testing with all the interactions, I am ok with this PR.
@nithusha21, I tried loading all_interactions exploration, but I had an error: Full proto too large to save, cleared variables. |
I've tried it and it's working fine. |
Does this error occur repeatedly if you try loading again? Normally that error message you mentioned is transient.
Could you catalog which interactions you've tested, and then manually test the remaining ones (if you can't load the "all interactions" exploration? You need to make sure no bugs get through and that you've manually examined the entire surface area. |
Okay. But, this PR is more of loading css with webpack since the bulk of the work was already done by @vojtechjelinek in #6939 |
Please still test all interactions comprehensively, and report the results back explicitly. We have had regressions in the past with the PRs for this project, and we should take steps to avoid that in the future. |
Okay. |
I confirm that I have tested this PR, I tried the all interactions explorations and everything works correctly. |
Thanks! Merging. |
Explanation
This PR removes the use of the jinja interaction template construct which currently holds css imports.
The css files are imported into their respective bundles via the webpack css-loader and style loader and hence fixes #6962
Checklist
python scripts/pre_commit_linter.py
andbash scripts/run_frontend_tests.sh
.