You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent 'upgrade' (via merge) of Guardian UI has introduced some PrimeNG components into the codebase, while most of the UI currently is based on Material UI. This is not ideal, complicates maintenance and extensibility, introduces another dependency tree etc.
Requirements
Standardize Guardian UI to be PrimeNG-based
Remove/Replace all Material UI components with PrimeNG ones without changing the look&feel
Definition of done
Fulfill the requirements as specified above
Update community contribution guidelines to require the use of PrimeNG-based components
Acceptance criteria
Only one component library is used in Guardian UI code
The text was updated successfully, but these errors were encountered:
prernaadev01
changed the title
Standardize UI on Angular Material, remove/replace PrimeNG
Standardize UI on primeNG remove/replace Angular material
Oct 22, 2024
Pyatakov
changed the title
Standardize UI on primeNG remove/replace Angular material
Standardize UI on PrimeNG and remove/replace Material UI components
Jan 27, 2025
Problem description
Recent 'upgrade' (via merge) of Guardian UI has introduced some PrimeNG components into the codebase, while most of the UI currently is based on Material UI. This is not ideal, complicates maintenance and extensibility, introduces another dependency tree etc.
Requirements
Definition of done
Acceptance criteria
Only one component library is used in Guardian UI code
The text was updated successfully, but these errors were encountered: