Skip to content

fix(styles): replace !important overrides with proper CSS specificity#565

Open
sawankshrma wants to merge 26 commits into
devsecopsmaturitymodel:gsoc2026from
sawankshrma:fix/remove-important-overrides
Open

fix(styles): replace !important overrides with proper CSS specificity#565
sawankshrma wants to merge 26 commits into
devsecopsmaturitymodel:gsoc2026from
sawankshrma:fix/remove-important-overrides

Conversation

@sawankshrma
Copy link
Copy Markdown
Collaborator

Replaces !important declarations across component stylesheets with
correct specificity-based selectors and Angular Material token APIs.
No visual changes intended.

wrap mat-icon in span with matListItemIcon to prevent MDC from overriding color=primary. After upgrading to Material 16, the icons became grey from the primary color they were
The --prod flag was deprecated in Angular CLI v12 and removed in later versions. Replaced with --configuration=production and dropped redundant --aot flag (AOT is default for production builds).
Removed eslint-config-standard-with-typescript and its peer deps (eslint-plugin-import, eslint-plugin-n, eslint-plugin-promise) — these were never referenced in .eslintrc.json and caused ERESOLVE peer dependency conflicts during the Angular 17 upgrade, as they pulled in incompatible ESLint/TypeScript version constraints that clashed with @angular-eslint v17. Also bumped eslint-config-prettier from ^8.5.0 to pinned 9.1.0 (v8.10.1 and v9.1.1 were compromised in a July 2025 supply chain attack), eslint-plugin-prettier to ^5.2.0, and prettier to ^3.3.0.
RouterTestingModule was deprecated in Angular v17 in favor of the standalone provideRouter() API.
moved MatChip from declarations to imports in circular-heatmap spec, since MatChip is now a standalone component in Angular Material 17 and cannot appear in declarations.
Ran ng lint --fix after bumping prettier from v2 to v3.
Angular 17 requires Node ≥18.13.0. Bump actions/checkout and actions/setup-node from v1 to v4 (v1 runs on deprecated Node 12).
No need to call ActivitiesBeingDisplayed every time the filter is changed as dataSource is a computed() value now which depends on other signal() values - levels, filtersTag and filtersDim
Consumers (AppComponent & SidNavButtonsCompoent) now use computed() values rather than subscribing to observables from these Services.
Switch from webpack-based browser builder to esbuild-based application builder. Fix markdown-it default imports, enable esModuleInterop, update polyfills to array format, remove webpack-only options (buildOptimizer, vendorChunk), remove polyfills.ts, and flatten output path to dist/dsomm/.
caused the duplicate color styles warning surfaced by the esbuild builder during ng serve
…e unnecessary styles (which were not affecting the UI)
…e.scss

the mat-expansinon-panel-header styles (48px and 16px) are anyways default values, removing them doesn't affect the UI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant