-
Notifications
You must be signed in to change notification settings - Fork 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
[HOLD for payment 2023-10-02] [$1000] Create a lint rule for unused styles and translation keys #22212
Comments
Triggered auto assignment to @NicMendonca ( |
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
No design changes here. Unassigning @shawnborton |
Hey, I am Edu from Callstack - an expert contributor group. I can work on this one |
Job added to Upwork: https://www.upwork.com/jobs/~0140cfa1480a9e4861 |
Current assignee @NicMendonca is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Working on handling deep storage per key, and searching |
Working on reading the styles and translation files, and adding tests compatible with JSX |
Need to work on another issue, couldn't work on it today |
@gedu any update here? |
That's awesome! Great work! |
@gedu is still working on the PR |
I'm currently resolving the conflicts, and I've added some comments to the PR. However, due to the new style format that incorporates a Theme object, I need to modify the way we retrieve and integrate these styles within the codebase. |
PR is still being worked on as per @gedu's update above |
@luacmartins PR updated, also found another unused style because a component was removed, so it is working great |
Awesome! Is the PR ready for review? |
@luacmartins Yes it is 🙌 |
@luacmartins Comments fixed and conflicts solved |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.73-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-02. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue: As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
![]() |
@NicMendonca correct, @fedirjh did not review that PR. |
ok cool, we're all set here then! |
Problem
We often add new styles to styles.js or copy to en.js and es.js, but when we remove the last instance using them in App, sometimes we forget to also remove their definition from
en.js
,es.js
orstyles.js
.Why is this important
Keeps the codebase clean
Solution
Add a lint rule to eslint-config-expensify to catch unused styles and translation keys so we can remove them appropriately.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: