-
Notifications
You must be signed in to change notification settings - Fork 4
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
build(web-client): upgrade to angular 13 #146
Conversation
✔️ Deploy Preview for affectionate-mirzakhani-7a7e75 ready! 🔨 Explore the source changes: 9f275b7 🔍 Inspect the deploy log: https://app.netlify.com/sites/affectionate-mirzakhani-7a7e75/deploys/622affd2fd3a5600081aea48 😎 Browse the preview: https://deploy-preview-146--affectionate-mirzakhani-7a7e75.netlify.app |
✔️ Deploy Preview for nautilus-wallet ready! 🔨 Explore the source changes: 9f275b7 🔍 Inspect the deploy log: https://app.netlify.com/sites/nautilus-wallet/deploys/622affd20eac3b0008158193 😎 Browse the preview: https://deploy-preview-146--nautilus-wallet.netlify.app |
Codecov Report
@@ Coverage Diff @@
## main #146 +/- ##
==========================================
- Coverage 66.66% 62.91% -3.75%
==========================================
Files 80 77 -3
Lines 801 747 -54
Branches 85 92 +7
==========================================
- Hits 534 470 -64
- Misses 267 277 +10
Continue to review full report at Codecov.
|
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.
Running npm install
:
57 vulnerabilities (2 low, 20 moderate, 34 high, 1 critical)
Can run npm audit fix
can fix a couple of vulnerabilities without any breaking changes:
46 vulnerabilities (2 low, 15 moderate, 29 high)
web-client/src/app/components/action-item/action-item.component.html
Outdated
Show resolved
Hide resolved
Waiting for Github Action checks to complete
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.
The ScannerPage test works locally, but fails intermittently in Github actions. As discussed in retro, we can approve and merge.
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.
Looks good. Thanks a lot for getting this sorted.
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.
- Follow-up: test(web-client): fix CI #160
The upgrade seems have broken the use of templateUrl
in the theme story: I'm not sure why, yet, but using an inline template
instead seems to work, so I did that as a workaround for the time being.
Follows: build(web-client): upgrade to angular 13 #146 This makes the CI pass again. * test(web-client): temporarily disable failing tests on CI * chore(web-client): .prettierignore: add Angular cache directory * style(web-client): npm run format * refactor(web-client): move lastValueFrom call This preserves the meaning of the "arrayBuffer" variable. * test(web-client): use inline template instead of templateUrl Upgrading to Angular 13 seems to have broken using templateUrl, but using an inline template still works, as a workaround for now.
No description provided.