Skip to content
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

Added explicit dependencies to ui-element-key-val-mapping #35718

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

orangejenny
Copy link
Contributor

Technical Summary

This is cherry-picked from the webpack migration for app manager. The rest of these widgets are used in other places and already declare their dependencies in the hqDefine call, but ui-element-key-val-mapping is apparently only used in app manager.

I also removed the overarching ui-element.js file that groups all of these widgets together. We don't use these widgets that widely, they don't need to be included as a unit. Including single widgets is how we handle other widget libraries (jquery ui, ko components).

Safety Assurance

Safety story

Tested locally that the icon mapping works in case detail. Smoke tested id mappings, inputs, and selects in case detail for good measure.

Automated test coverage

doubt it

QA Plan

Not requesting QA.

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

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

@orangejenny orangejenny added the product/invisible Change has no end-user visible impact label Jan 31, 2025
@orangejenny orangejenny requested a review from biyeun as a code owner January 31, 2025 06:24
return hqImport('hqwebapp/js/ui_elements/bootstrap3/ui-element-key-val-mapping').new(options);
};

module.serialize = function (obj) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this unused? I didn't see anywhere where it is replaced in this PR.

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