-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Angular 18 upgrade (squashed) #500
Conversation
…lar, CDK, ESLint, PWA, and Material dependencies.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good. No comments - surprising for such a large PR. Good work!
I have noticed that when tests hang, they tend to be related to AG Grid. They don't fail, but they hang. Presumably the issues @gsambrotta found on the Vercel preview are not covered by our current tests - I suggest we remedy this. |
Thanks both, good finds, I was adding to the description about the changes with the grid version upgrade and key patterns in the file changes of this when you added this! |
…efect visible on the Flow at workflowCloud/listWorkflows which has a grid used that had wrongly overlapping text.
Looks good now @lukestanley |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, you are right, I did not commit the other comments. Here they are
…es it -Adds waiting assertions to ensure test starts in correct state -Simplified logic, used constants for readability and robustness.
9505bb4
to
f3259da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All tests passing, no comments. Good stuff - approved!
Looks good to me now. |
Introduces Angular 18 compatibility, compatible Monaco Editor, Ag Grid issues, adds identifiers for Cypress tests to find, UI compatibility refactoring, styling and code clean-up, built on top of Gio's and J Black's work.
There were over 70 commits built on an old base branch, so to avoid introducing unintended regressions and to make sensible review process more possible, I rebuilt it as 6 commits, that merge diff patches from key commits. Many unneeded linting changes were removed. About half as many lines are used, and a lot less files are changed too.
I removed unrelated documentation changes and based it on develop so it will merge.
Angular & Dependency Upgrades
MatLegacy*
imports with currentMat*
components.mat-menu-item
to.mat-mdc-menu-item
)appearance="outlined"
for Material input fieldsmain.ts
Monaco Editor
Ag Grid UI fixes
Component and UI Refactoring
mat-label
for accessibilityangular2-text-mask
withmaskito
for input maskingminlength
tominLength
)Testing
data-cy
attributes for more reliable Cypress selectionesModuleInterop
Styling & Code Clean-up
Risk Areas to Review
maskito
input masking reliabilitydata-cy
attributes and overall test stabilityA more complete history may be helpful context, there are 117 commits in angular-18-upgrade-rebase: https://github.com/kendraio/kendraio-app/pull/496/commits (draft PR for easier reference that has filtering features the tree comparison view does not).
It builds, and tests are passing!
I noticed warnings, during build, that match the warnings in Gio's pull request so they are not a regression upon that.
I am not sure how to best include tasks and reference information that is on #487 backing up the existing angular-upgrade-18 branch and force merging this would help, and I am open to other ideas to ensure we don't loose the insights there. Discuss!
We are still on the look out for possible reactivity regressions. If we can get this (or something based on this) on production we can test it in a more realistic setting than the Vercel build.
The Vercel build is here.
Please review carefully, especially test changes, and there was a lot of manual work merging style changes, so there is greater risk of error there.