-
-
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 16 #425
base: develop
Are you sure you want to change the base?
Angular 16 #425
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
26fb79c
to
759d6b3
Compare
// this time we got there | ||
cy.location().should((loc) => { | ||
expect(loc.pathname).to.eq('/dashboard'); | ||
}); | ||
}) | ||
|
||
*/ |
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.
Need an issue for this too.
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.
Now there is an issue for it: #428
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.
Add the issue to the code comment?
{ | ||
"type": "form", | ||
"hasSubmit": true, |
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.
Added the submit button to avoid state bug.
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.
Again, a related issue was made for this:
#429
|
||
cy.intercept('GET', 'https://app.kendra.io/api', { | ||
fixture: 'flowList.json' | ||
} | ||
).as('flowList.json'); | ||
|
||
cy.visit('/workflowCloud/listWorkflows'); | ||
cy.contains('Submit').click(); |
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.
I made an issue for this change: #429
It might be a complex and tricky "can of worms".
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.
Yeyyy!!! 🎉 🎉 🎉
Well done @lukestanley, amazing work 👏 👏 👏
Code wise, it looks pretty good to me. I left some minor comments.
About the UI test, I am checking the vercel url: https://kendraio-app-git-angular-16-kendraio.vercel.app
1_ Here: https://kendraio-app-git-angular-16-kendraio.vercel.app/connect they UI looks different then in the production app. I also don't see the "Connect" button.
2_ Grid header and Button label seems to have a different font: https://kendraio-app-git-angular-16-kendraio.vercel.app/core/adapters.
3_ Sidemenu items are back to be label Workflow
instead of Flow
5_ Grid design is different and I would say less good looking then what we had previously
6_ When I go to Flow Cloud I do not see the flows at the first render. I do see the flows if I search for them.
7_ Flow cloud flows do not have a "Launch" button so I cannot open them
8_ Some design is off like this
@@ -7,15 +7,16 @@ import { EDITOR_OPTIONS } from './editor-options'; | |||
import JSONFormatter from 'json-formatter-js'; | |||
import {get, has, isString} from 'lodash-es'; | |||
import {BehaviorSubject} from 'rxjs'; | |||
import '@angular/material/tooltip'; |
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.
Why is this imported here? Was previously part of the MatDialog
and now they are separate?
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.
If so, why is not also imported in the below file settings-page-component.ts
, where the same MatDialog
is used?
} | ||
|
||
@import "~@fortawesome/fontawesome-free/css/all.css"; | ||
@import "@fortawesome/fontawesome-free/css/all.css"; |
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.
Is correct that the first world is @fortawesome
? Is a mistype from the fontawesome team ? :D
cypress/e2e/gosub.ts
Outdated
@@ -24,7 +24,7 @@ describe('Subroutine workflow block', () => { | |||
"workflowId": "madeUpFlowIDA" | |||
} | |||
]); | |||
cy.get('mat-toolbar > button mat-icon').contains('settings').click(); | |||
cy.get('mat-toolbar > button mat-icon').contains('settings').click({force: true}); |
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.
Why do we need this force: true
?
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.
We may not with the new Cypress version! I need to check.
// this time we got there | ||
cy.location().should((loc) => { | ||
expect(loc.pathname).to.eq('/dashboard'); | ||
}); | ||
}) | ||
|
||
*/ |
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.
Add the issue to the code comment?
Thanks! Not all me, of course!
This is problematic! Maybe the warning I just found is related?
This is undesirable, an issue for this and other styling issues is a good idea, I think.
Did you have a 4th point? I noticed you had a numbered list with a missing 4 :)
I noticed a console warning just now, that suggests a version change has broken some functionality. Missing buttons for example, I think are much more serious than the style problem/s.
|
@gsambrotta can look at these problems:
|
I made #435 to track the state reactivity issues. |
…re fix, removes ngModelGroup. Materia-ui module was stale. Prior setDiagnosticOptions configuration caused error due to missing object. The ngModelGroup template property also caused runtime error and is not needed.
…span child element covering is acceptable.
…ting! Needs fixing later!
* restore correct UI style to grid * apply breaking changes with frmeworkComponents, bump version to 31
* migrate with ng generate, fix card style * adjust dialogs * fix block comment textarea UI * clean up main.scss * fix connect to user link * update test script with develop, fix datagrid disable test
3de93d8
to
dd2bed0
Compare
Issues on
|
This upgrades to Angular 16, now it's Ivy engine is in use, bringing along various changes and enhancements to the existing codebase.
The key highlights include:
Upgrading Angular dependencies.
Material UI Components Update: Accompanying the Angular upgrade, the Material UI components have been updated to their latest versions. This update involved replacing legacy Material components with their current counterparts, ensuring a smoother UI experience and compatibility with Angular 16.
Form and Query Builders fix - Monaco Editor package switch: A significant change in this PR is the switch from @materia-ui/ngx-monaco-editor to ngx-monaco-editor-v2. This change was because the old materia-ui package had no compatible update available, there were runtime errors encountered with Angular 16 that broke the Form and Query Builders. Fixing Monaco Editor path issue - the configuration for Monaco Editor has been adjusted so it can load properly also.
Cypress Test Adjustments: To adapt to the changes in the UI components and the new Angular version, several Cypress tests have been modified. This includes updates to selectors and the introduction of forced clicks in scenarios where elements were being obscured, thereby addressing test failures post-upgrade. Some of these changes might be revereted now Cypress has been upgraded, they might not be needed!
Code Refinements and Cleanup: Prettifier / linting changes (sorry! I didn't do it! I reverted some for readability but there are a lot!), removal of unused imports like CanDeactivate from Angular Router, updates to TypeScript versions.
Correcting outdated Formly validation properties.
CommonJS compilation bailout warnings: To resolve console warnings I added a Lodash to an allowed list. More resources may need adding if similar warnings still show.
I cherry-picked the commits on top of develop and resolved some merge conflicts ahead of time.
A way to re-do the same linting / "prettifier" changes on develop could help reduce the diff. So far, I wasn't able to figure out how to do that in a way that gives the same results.
One key concern is that state reactivity issues in Flows may be happening more often than before, this is a possible regression. See this issue.