Revert cc global in favour of legacy files#178
Merged
Conversation
brylie
approved these changes
Feb 4, 2022
Contributor
|
@all-contributors please add @MuluhGodson for code |
Contributor
|
I've put up a pull request to add @MuluhGodson! 🎉 |
This file contains hidden or 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
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.
Fixes
Fixes https://github.com/creativecommons/project_creativecommons.org/issues/208 by @MuluhGodson
Description
This PR removes the CC-Global-Components and replaces them with the legacy files.
Technical details
The CC Global package is developed with vue 3 and this is a conflict when the chooser package is integrated since it is developed with vue 2. For the MVP, it is sufficient to remove cc-global in favour of the legacy files. These will subsequently be updated later when chooser is upgraded to Vue 3.
Screenshots
Checklist
Update index.md).mainormaster).visible errors.
Developer Certificate of Origin
For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."
Developer Certificate of Origin