-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
[FLINK-23111][runtime-web] Bump angular's and ng-zorro's version to 12 #16603
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit afabfeb (Tue Jul 27 08:23:31 UTC 2021) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
afabfeb
to
10e6627
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.
Changes look good to me, thanks!
BTW, I'm also totally fine with doing the upgrades all the way to Angular 12 on the same PR. Just separating by commit to make it easier to review would be appreciated, but we don't need to wait on merges every single time that way. |
Sure, I will continue to push commits to this PR. |
@Airblader I believe this PR is ready for reviews now. BTW, since there is little modifications while bumping from v11 to v12, I have merged those two updates in one commit. |
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.
Thanks for working on this! Overall it looks great. I left a couple minor comments. There is one main thing we need to do still, however; we need to update the pom.xml
to use a compatible node version (12.14.x/14.15.x or later minor version) during a Maven build.
"zone.js": "~0.8.26" | ||
"monaco-editor": "^0.20.0", | ||
"ng-zorro-antd": "^12.0.1", | ||
"rxjs": "^6.5.3", |
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 should be >= 6.6 (see https://gist.github.com/LayZeeDK/c822cc812f75bb07b7c55d07ba2719b3)
"@angular/forms": "~12.1.3", | ||
"@angular/platform-browser": "~12.1.3", | ||
"@angular/platform-browser-dynamic": "~12.1.3", | ||
"@angular/router": "~12.1.3", | ||
"@antv/g2": "^3.4.10", | ||
"core-js": "^2.5.4", | ||
"d3": "^5.9.1", | ||
"d3-flame-graph": "^4.0.6", | ||
"d3-tip": "^0.9.1", | ||
"dagre": "^0.8.4", |
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 should add dagre
to allowedCommonJsDependencies
in angular.json
to avoid a warning.
779a268
to
a26f2ff
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.
Thanks! Let's wait for the CI, but LGTM now.
@Airblader I believe the CI has finished. Once this PR is merged, I can start working on the eslint migration. |
Sounds great. Do you have someone who can merge this PR for you? Otherwise I can find someone who can take care of it. |
Please do so. I have no one to do it for me currently. |
That's fine. We'll take care of it. |
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.
Thanks for improving the web UI @yangjunhan. I can help merging this but have to rely on @Airblader judgement for a review. One thing that we should check though is whether we need to update NOTICE files. I see flink-runtime-web/src/main/resources/META-INF/NOTICE
maybe also in flink-dist
?
Hi, @Airblader @twalthr. How is the reviewing going? Could you kindly confirm whether I need to update the |
@yangjunhan Yes, the NOTICE file @twalthr mentioned needs to be updated as well. |
Okay, I will handle it @Airblader . However, I am not very sure the tool and exact steps to auto-update the NOTICE file, and I do not think that I should manually update the file 😂. BTW, would it be possible to invite me to the Veverica Slack workspace so that we can communicate there in a more convenient way? I am currently a team member of VVP Front-end in Hangzhou, China. |
I actually think the NOTICE files are maintained manually (unfortunately). There is a license checker to verify some basic things, but I am not sure it even runs for the npm dependencies. I'll try to ask someone about Slack and will get back to you. |
@yangjunhan Can you give us your email address with which to invite you to Slack? |
My email address: yangjunhan1234@gmail.com. Thanks. |
supersedes #14960 |
…untime-web-bump-8
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.
LGTM
…ndencies, and NOTICE This closes apache#16603.
…ndencies, and NOTICE This closes apache#16603.
What is the purpose of the change
Step-by-step modernize flink-runtime-web, i.e. Flink UI.
Brief change log
Bump to the latest version of Angular and NG-Zorro.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: noDocumentation