-
Notifications
You must be signed in to change notification settings - Fork 80
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
refactor: upgraded frontend-build version to v12 #322
Conversation
Codecov ReportBase: 74.26% // Head: 74.45% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #322 +/- ##
==========================================
+ Coverage 74.26% 74.45% +0.19%
==========================================
Files 106 106
Lines 2067 2083 +16
Branches 512 514 +2
==========================================
+ Hits 1535 1551 +16
Misses 504 504
Partials 28 28
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. |
… into bilalqamar95/frontend-build-upgrade
…nto bilalqamar95/frontend-build-upgrade
…nto bilalqamar95/frontend-build-upgrade
Internal team ticket: https://2u-internal.atlassian.net/browse/TNL-10269 |
…nto bilalqamar95/frontend-build-upgrade
@jristau1984, looks like this is passing checks - anything else that needs to be done? |
With such a big scope of change, some smoke tests in a lower environment would be ideal. After/barring that, just please let our on-call know you plan to merge. Thanks! |
@jristau1984, my plan is to press the merge button here tomorrow morning. |
Sounds good. Flagging @connorhaugh as on-call for the week. |
This change appears to have broken the Pages an Resources pages. 2U-internal ticket: https://2u-internal.atlassian.net/browse/TNL-10439. This will be triaged and likely reverted to ensure our pipeline can be re-enabled. @bszabo is now on-call, and will be fielding this effort. |
@jristau1984, that's unfortunate. Do we have any details regarding what exactly is broken and how, by any chance? |
@arbrandes - This is the information we know at this time, since our current SOP is to triage and revert rather than dig into root cause. Steps to repro:
Error: Please let us know if we can be of further assistance! |
@jristau1984 The error message is indicating that an object is being rendered as a child component, I have tracked the issue & it is coming from CourseAuthoringPage, due to changes made in this PR. There may be some issue in the implementation of AppHeader component. It could be that some prop or component state is an object instead of a valid React child component. Since the revert has not been merged yet, I have fixed the issue, here is a PR for it with the fix. |
Thanks for fixing this, @BilalQamar95! |
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