Skip to content

Conversation

@nospame
Copy link
Contributor

@nospame nospame commented Dec 18, 2025

Technical Summary

https://dimagi.atlassian.net/browse/SAAS-18984
Splits App Manager to begin Bootstrap migration for the app; does not migrate anything yet.

The last commit was done manually and modifies webpack config to build b3 and b5 versions of a couple specific app manager files correctly. The rest are all automated, with:

./manage.py migrate_app_to_bootstrap5 app_manager --skip-all

Apologies for the size of this PR - that's just the size of the app_manager django app.

Safety Assurance

Safety story

Spot tested locally using vellum debug (i.e. vellum running from submodules/formdesigner) both on and off, as well as on staging.

Automated test coverage

For bootstrap diffs.

QA Plan

Not for this initial split.

Rollback instructions

  • This PR can be reverted after deploy with no further considerations
    This split can be reverted easily only if there have been no further changes in app_manager following its being merged.

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

…als/modules/module_view_case_type.html, splitting templates"
…als/appnav_menu_header.html, splitting templates"
…als/releases/app_release_logs.html, splitting templates"
…als/forms/form_view_modals.html, splitting templates"
…als/toggle_diff_modal.html, splitting templates"
…als/modules/case_tile_templates.html, splitting templates"
…als/releases/build_profiles.html, splitting templates"
…als/forms/form_tab_advanced.html, splitting templates"
…als/menu/appnav_menu.html, splitting templates"
…als/releases/releases_deploy_modal.html, splitting templates"
…als/modules/mobile_report_configs.html, splitting templates"
…als/forms/form_workflow.html, splitting templates"
…als/app_summary_button.html, splitting templates"
…als/modules/case_list_lookup.html, splitting templates"
…als/download_async_modal.html, splitting templates"
…als/forms/custom_assertions.html, splitting templates"
…als/settings/supported_languages.html, splitting templates"
…als/forms/shadow_parent_select.html, splitting templates"
…als/forms/case_config.html, splitting templates"
…als/modules/case_search_properties.html, splitting templates"
…als/releases/releases_deploy_modal_sms.html, splitting templates"
…als/releases/releases.html, splitting templates"
…als/module_options/module_option_report.html, splitting templates"
…als/module_options/module_option_survey.html, splitting templates"
…als/module_options/module_option_advanced.html, splitting templates"
…als/module_options/module_option_shadow.html, splitting templates"
…als/module_options/module_option_training.html, splitting templates"
…als/module_options/module_option_biometrics.html, splitting templates"
…als/nav_menu_media.html, splitting templates"
…als/module_options/module_option_shadow_v1.html, splitting templates"
…als/module_options/module_option_case.html, splitting templates"
…dules/module_view_report.js, splitting templates"
@nospame nospame added the product/invisible Change has no end-user visible impact label Dec 18, 2025
@nospame nospame marked this pull request as ready for review December 18, 2025 23:45
@nospame nospame requested a review from mkangia as a code owner December 18, 2025 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product/invisible Change has no end-user visible impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants