Skip to content
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

Standardize UI on PrimeNG and remove/replace Material UI components #3141

Closed
anvabr opened this issue Jan 22, 2024 · 0 comments
Closed

Standardize UI on PrimeNG and remove/replace Material UI components #3141

anvabr opened this issue Jan 22, 2024 · 0 comments

Comments

@anvabr
Copy link
Collaborator

anvabr commented Jan 22, 2024

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

  • 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

@prernaadev01 prernaadev01 changed the title Standardize UI on Angular Material, remove/replace PrimeNG Standardize UI on primeNG remove/replace Angular material Oct 22, 2024
@Pyatakov 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants