chore!: replace @edx/paragon and @edx/frontend-build to use openedx namespace #530
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #530 +/- ##
=======================================
Coverage 71.94% 71.94%
=======================================
Files 51 51
Lines 802 802
Branches 156 156
=======================================
Hits 577 577
Misses 215 215
Partials 10 10 ☔ View full report in Codecov by Sentry. |
… into mashal-m/replace-edx/paragon-frontend-build
… into mashal-m/replace-edx/paragon-frontend-build
abdullahwaheed
changed the title
abdullahwaheed
deleted the
mashal-m/replace-edx/paragon-frontend-build
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Part of openedx/axim-engineering#23
This replaces the
@edx/paragonand@edx/frontend-buildpackage.Imports have been updated to use the same locations in the new package.