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

Update dependencies and documentation #130

Merged
merged 21 commits into from
May 20, 2022
Merged

Update dependencies and documentation #130

merged 21 commits into from
May 20, 2022

Conversation

boeckMt
Copy link
Member

@boeckMt boeckMt commented May 18, 2022

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Update to Angular v13 should be made.

What is the new behavior?

  • Update Angular to v13 and other dependencies 13735d2, 95d7724, 940e526
  • Update Node in CI for Angular update da1260d, 99d2f8e, 99d2f8e, 1f4a91a, dab8a01
  • fix some type errors in @dlr-eoc/core-ui schematics and add skipLibCheck on ng-add to tsconfig 55e7700, 5f146b4, 68abb5b
  • fix some type errors in @dlr-eoc/user-info for AbstractControl from FormGroup 83549df
  • fix some type errors for OffscreenCanvas in demo-maps, demo-auth, '@dlr-eoc/map-ol', @dlr-eoc/map-three, @dlr-eoc/map-tools and @dlr-eoc/utils-maps 33be2fe

Does this PR introduce a breaking change?

  • Yes
  • No

Update Angular to v13 and ol-mapbox-style to v8

Other information

Is it part of one/more packages and which?

  • All @dlr-eoc due to Angular update

Copy link
Collaborator

@MichaelLangbein MichaelLangbein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing to add! Looks good to me!

@@ -94,7 +94,7 @@ jobs:
path: dist
- uses: actions/setup-node@v2
with:
node-version: 15
node-version: 16
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool thing that we're moving up to node16. I think I remember that older versions of node/npm would create an old-style package-lock v1.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think this was between npm 6 and 7.
We only have one Issue to fix for the publish step #129 where we use npm 6. But we don't install anything here, it's just for the publish command so I hope this is still working with the newer node version.

@@ -78,15 +78,15 @@ main-container
content-area
```

and be aware that the router is placing the routes outside of the router-outlet (so they are not childs)
and keep in mind that the router is placing the routes outside of the router-outlet (so they are not childs)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... (so they are not children)

Copy link
Contributor

@lucas-angermann lucas-angermann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have nothing to add as well!

@boeckMt boeckMt merged commit 49acfae into main May 20, 2022
@boeckMt boeckMt deleted the update-ng branch May 20, 2022 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants