-
Notifications
You must be signed in to change notification settings - Fork 467
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
Remove lodash
from core-web
#24842
Comments
1- patch it |
It's a front-end component. |
FYI, new version is .21 |
@fmontes - please take it forward. Do we need to remove lodash, or should we upgrade to newer version? |
Note to QAPlease be sure that all the portlets where the Template Builder is present, works as expected. I removed the Old Template Builder code, because it had |
### Proposed Changes * Replace `lodash` with native functions * Remove unused and bloated code * Remove the FF Checking to decided between old and new Template Builder, since we are not supporting the old one anymore * Remove old Template Builder from the code * Change a `setTimeout` time from `250` to `350` to cover an unknown edge case to prevent a bad UX animation to be seen by the user (This change is UX related, does not affect any functionality)
Passed IQAtested in master Screen.Recording.2024-08-27.at.4.23.14.PM.mov |
Fixed, I made a smoke validation on containers and pages and everything is working normally! |
Parent Issue
No response
Task
lodash
is problematic and has security issues, besides we're not using it a lot.Let's remove
lodash
.Proposed Objective
Security & Privacy
Proposed Priority
Priority 2 - Important
Acceptance Criteria
lodash
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: