-
Notifications
You must be signed in to change notification settings - Fork 16
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
Feature/seab 6279/angular material #2052
base: develop
Are you sure you want to change the base?
Conversation
in the facets page
to normal.
although now they're a little high
Maybe fix services tests. Fix padding issues with details page.
ngx-mat-select-search
Quality Gate failedFailed conditions See analysis details on SonarQube Cloud Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE |
Latest status before transferring this. The good news is all integration and unit tests are passing. The bad news is:
Dashboard, padding around Register Workflow button not right, plus Dropdown on files tab has wrong background color, perhaps wrong font Horizontal scrolling has crept back into versions tab, probably a font size issue, but just guessing Left-side of dashboard totally off, padding, colors Organizations page, content between different boxes not aligning. Compare to prod where the divider lines up exactly between boxes on the same row Home page, starred-entries page. "chips" are larger, with the bonus of throwing off the wrapping on the home page |
Description
Upgrades to Angular MDC Material from the legacy components we are using today.
Why? Because Angular Material 17 dropped the legacy components. This means we can't upgrade to Angular 17 and stay current. Angular 16, our current version, is already no longer actively supported.
The Migration
Review Instructions
Describe if this ticket needs review and if so, how one may go about it in qa and/or staging environments.
For example, a ticket based on Security Hub, Snyk, or Dependabot may not need review since those services
will generate new warnings if the issue has not been resolved properly. On the other hand, an infrastructure
ticket that results in visible changes to the end-user will definitely require review.
Many tickets will likely be between these two extremes, so some judgement may be required.
Issue
A link to a github issue or SEAB- ticket (using that as a prefix)
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!
npm run build
markdown-wrapper
component, which does extra sanitizationnpm audit
and ensure you are not introducing new vulnerabilities