-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
[B5 Migration] Add support for ES6 Modules and split core javascript into bootstrap5 and bootstrap3 versions (take 2) #33083
Conversation
… of our javascript libraries separately
…ld doesn't break on hqwebapp/js/500
…on the bootstrap3 or 5 version and make sure use_bootstrap5 is in template context
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.
This is a "revert" of #32907
Did you mean "redo" instead of "revert"? The first commit in that other PR looks the same as the first commit in this one, not like a reversal.
Can you point out what changed between this PR and the previous one since it's quite large?
It's more of a redo because a change was committed to HQ to |
@millerdev the last two commits are the only differences |
This is a "revert" of #32907
Note that these changes have properly gone through QA on staging and signed off.
This commcare-cloud PR was key in resolving the symptoms of the issue, ensuring that no live bootstrap 3 pages were affected. I will revisit the more longterm fix for bootstrap 5 pages after I've taken a pass at writing the migration helper scripts.
Related ticket: https://dimagi-dev.atlassian.net/browse/SAAS-14253
Safety Assurance
Safety story
QA'd successfully
Automated test coverage
Yes
QA Plan
Yes
Rollback instructions
Labels & Review