End-user friendly description of the problem this fixes or functionality that this introduces
We have a pretty inconsistent file naming convention used throughout the frontend portion of the app.
[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below
Give a summary of what the PR does, explaining any non-trivial design decisions
Add consistency to all file and directory names to be of kebab-case (nice on the eyes, personal preference)
Apply eslint / prettier formats to some components
Git CI
Clear TS cache
Clear Git cache
When working in environments like GitHub CI, file name conflicts arise because Git treats file names as case-insensitive (on case-insensitive file systems like macOS or Windows), while TypeScript treats file names as case-sensitive. This leads to errors when files with mismatched casings are resolved differently in the CI environment, especially on case-sensitive systems like Linux.
To address this, we need to clear both the TypeScript cache and Git cache during the build process.
Follow-up PRs
Remove unused components
Merge duplicate components
Organize components into folders
To run this PR locally, use the following command:
End-user friendly description of the problem this fixes or functionality that this introduces We have a pretty inconsistent file naming convention used throughout the frontend portion of the app.
Give a summary of what the PR does, explaining any non-trivial design decisions
kebab-case
(nice on the eyes, personal preference)Git CI
When working in environments like GitHub CI, file name conflicts arise because Git treats file names as case-insensitive (on case-insensitive file systems like macOS or Windows), while TypeScript treats file names as case-sensitive. This leads to errors when files with mismatched casings are resolved differently in the CI environment, especially on case-sensitive systems like Linux.
To address this, we need to clear both the TypeScript cache and Git cache during the build process.
Follow-up PRs
To run this PR locally, use the following command: