-
Notifications
You must be signed in to change notification settings - Fork 212
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
Updated frontend-build to v12 #962
Conversation
Codecov ReportBase: 86.68% // Head: 86.83% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #962 +/- ##
==========================================
+ Coverage 86.68% 86.83% +0.15%
==========================================
Files 252 252
Lines 4295 4329 +34
Branches 1097 1096 -1
==========================================
+ Hits 3723 3759 +36
+ Misses 553 551 -2
Partials 19 19
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@BilalQamar95, do you mind resolving conflicts? Thanks! |
.github/workflows/validate.yml
Outdated
@@ -12,11 +12,13 @@ jobs: | |||
strategy: | |||
matrix: | |||
node: [16] | |||
npm: [8.5.x] |
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.
Do we need to check this? I think it is probably more reasonable to check just 8. Not all of node@16 correspond to npm@8.5.
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 check was added to resolve ci
dependency issues
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.
There seems to be some issue with your package-lock.json
if the ci
fail. For example, this pr no longer have package.json
change and yet package-lock.json
persist. I would suggest remove this and package-lock.json
.
There is recent change to upgrade |
src/course-home/progress-tab/grades/grade-summary/GradeSummaryTable.jsx
Outdated
Show resolved
Hide resolved
src/course-home/progress-tab/grades/grade-summary/GradeSummaryTable.jsx
Outdated
Show resolved
Hide resolved
src/course-home/progress-tab/grades/grade-summary/GradeSummaryTable.jsx
Outdated
Show resolved
Hide resolved
src/course-home/progress-tab/grades/grade-summary/GradeSummaryTable.jsx
Outdated
Show resolved
Hide resolved
9d56d84
to
24d3345
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.
I made a couple change by rebasing the change then remove package-lock.json
and .github/workflows/validate.yml
. I tested with everything working.
* feat: rebase previous frontend-build upgrade * chore: make welcome message to default to empty
* feat: rebase previous frontend-build upgrade * chore: make welcome message to default to empty
* feat: rebase previous frontend-build upgrade * chore: make welcome message to default to empty
Ticket:
42: Upgrade eslint to v8.x
What changed?
frontend-build
to v12 (Eslint was updated infrontend-build
version resulting in it's version being bumped to v12. This PR updatesfrontend-build
to reciprocate eslint version update)eslint
issues post update