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

Bump Angular to v10, TypeScript to 3.9 and use ESNext #2456

Merged
merged 18 commits into from
Jul 7, 2020

Conversation

maciaszczykm
Copy link
Contributor

@maciaszczykm maciaszczykm commented Jul 3, 2020

What this PR does / why we need it: https://volosoft.com/blog/what-is-new-in-angular-10

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #2448.

Special notes for your reviewer:

Release note:

NONE

@kubermatic-bot kubermatic-bot added the release-note-none Denotes a PR that doesn't merit a release note. label Jul 3, 2020
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maciaszczykm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jul 3, 2020
@codecov
Copy link

codecov bot commented Jul 3, 2020

Codecov Report

Merging #2456 into master will decrease coverage by 8.13%.
The diff coverage is 86.66%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2456      +/-   ##
==========================================
- Coverage   65.19%   57.06%   -8.14%     
==========================================
  Files         283      283              
  Lines       11589    11165     -424     
  Branches     1460     1443      -17     
==========================================
- Hits         7556     6371    -1185     
- Misses       4022     4783     +761     
  Partials       11       11              
Impacted Files Coverage Δ
...er-settings/alibaba-provider-settings.component.ts 55.26% <ø> (-6.28%) ⬇️
...ovider-settings/aws-provider-settings.component.ts 55.26% <ø> (-6.28%) ⬇️
...ider-settings/azure-provider-settings.component.ts 50.00% <ø> (-4.72%) ⬇️
...ttings/digitalocean-provider-settings.component.ts 61.29% <ø> (-7.46%) ⬇️
...ovider-settings/gcp-provider-settings.component.ts 61.29% <ø> (-7.46%) ⬇️
...er-settings/hetzner-provider-settings.component.ts 61.29% <ø> (-7.46%) ⬇️
...r-settings/kubevirt-provider-settings.component.ts 61.29% <ø> (-7.46%) ⬇️
...-settings/openstack-provider-settings.component.ts 58.33% <ø> (-6.54%) ⬇️
...er-settings/vsphere-provider-settings.component.ts 52.50% <ø> (-6.04%) ⬇️
...ared/components/event-list/event-list.component.ts 43.13% <0.00%> (-12.64%) ⬇️
... and 248 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 27f7d1f...6f372ff. Read the comment docs.

@maciaszczykm maciaszczykm marked this pull request as draft July 3, 2020 09:23
@kubermatic-bot kubermatic-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 3, 2020
@maciaszczykm maciaszczykm force-pushed the update/dependencies branch from 3dbc8e9 to 6805984 Compare July 3, 2020 12:27
@kubermatic-bot kubermatic-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 3, 2020
@kubermatic-bot kubermatic-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 6, 2020
Marcin Maciaszczyk added 2 commits July 6, 2020 11:46
@maciaszczykm maciaszczykm changed the title Bump Angular to v10 Bump Angular to v10, TypeScript to 3.9 and use ESNext Jul 6, 2020
@maciaszczykm
Copy link
Contributor Author

maciaszczykm commented Jul 6, 2020

@kgroschoff It seems that I have find solution for the existing issues:

  • Font Awesome is now completely removed. It was mainly used to display solid circle (status icon) and loading spinner that were replaced by custom SVGs. There were also 2-3 icons that were replaced by Material Icons.
  • ngx-custom-validators had to be reverted to v8.0.0 as it was not working after Angular update.
  • Ubuntu font is now installed with fontsource-ubuntu dependency, thanks to it we are not keeping any font assets in our src directory.
  • ES5 is no longer supported by Angular 10, I've switched to "esnext" that should allow us to follow the updates.

Please take a look :)

@maciaszczykm maciaszczykm marked this pull request as ready for review July 6, 2020 11:17
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 6, 2020
@maciaszczykm
Copy link
Contributor Author

/test test-e2e

@maciaszczykm
Copy link
Contributor Author

Build was failing because Subject was imported from rxjs/Subject instead from rxjs directly in a few places. Good to remember for the future.

@kgroschoff
Copy link
Contributor

Nice work 👍

I only noticed one error in the browser console:

Refused to apply style from 'http://localhost:8000/assets/fonts/material_icons/material-icons.css' because its MIME type
('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Do you also see it?

Otherwise LGTM, couldn't find any other problems 👍

@maciaszczykm
Copy link
Contributor Author

@kgroschoff It is fixed now. There was a reference to the old file.

@kgroschoff
Copy link
Contributor

Great 😃
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2020
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 073ec0acc580e3e680bccd15c605c77fbf963ffd

@kgroschoff
Copy link
Contributor

/hold
not sure if you want to merge other stuff first. feel free to unhold :)

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2020
@maciaszczykm
Copy link
Contributor Author

/retest
/hold cancel

@kubermatic-bot kubermatic-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2020
@kubermatic-bot kubermatic-bot merged commit 1293052 into kubermatic:master Jul 7, 2020
@maciaszczykm maciaszczykm deleted the update/dependencies branch July 7, 2020 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump Angular to v10
3 participants