Skip to content

feat: Revert ability to create Legacy Libraries#3077

Open
salman2013 wants to merge 1 commit into
openedx:masterfrom
salman2013:salman/remove-legacy-library
Open

feat: Revert ability to create Legacy Libraries#3077
salman2013 wants to merge 1 commit into
openedx:masterfrom
salman2013:salman/remove-legacy-library

Conversation

@salman2013
Copy link
Copy Markdown
Contributor

@salman2013 salman2013 commented Jun 3, 2026

Description

In this PR, we reverted the code that added the ability to create legacy libraries.
Ref: #2551

Ticket: openedx/openedx-platform#38056

Testing instructions

Getting there:

  • Open Studio, log in as staff / course creator
  • Go to the "Legacy Libraries" tab
  • Hit "+ New Library"
  • You should brought to the new CreateLegacyLibraries page.

Test v2 CreateLibrary unchanged:

  • In Studio, go to the "Libraries (Beta)" tab
  • Hit "+ New Library"
  • You should be brought to the regular v2 "Create Library" page.

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

  • Any new files are using TypeScript (.ts, .tsx).
  • Avoid propTypes and defaultProps in any new or modified code.
  • Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
  • Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
  • Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
  • All new i18n messages in messages.ts files have a description for translators to use.
  • Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Jun 3, 2026
@openedx-webhooks
Copy link
Copy Markdown

openedx-webhooks commented Jun 3, 2026

Thanks for the pull request, @salman2013!

This repository is currently maintained by @bradenmacdonald.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.61%. Comparing base (3f531d5) to head (635845a).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3077      +/-   ##
==========================================
- Coverage   95.61%   95.61%   -0.01%     
==========================================
  Files        1391     1386       -5     
  Lines       33075    32995      -80     
  Branches     7680     7424     -256     
==========================================
- Hits        31626    31548      -78     
- Misses       1384     1394      +10     
+ Partials       65       53      -12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR removes the in-app “Create Legacy Library” flow and instead routes legacy-library creation users to the Studio “home_library” page via a direct URL.

Changes:

  • Update StudioHome “New library” behavior for legacy (v1) libraries to open ${STUDIO_BASE_URL}/home_library.
  • Update StudioHome tests to assert window.open is called instead of SPA navigation.
  • Remove legacy library creation UI/API/hooks/messages and the /libraries-v1/create route/export.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
src/studio-home/StudioHome.tsx Opens legacy library creation via window.open to home_library instead of client-side routing.
src/studio-home/StudioHome.test.tsx Updates expectation to window.open for legacy library creation.
src/library-authoring/index.tsx Removes export for legacy library creation component.
src/library-authoring/create-legacy-library/messages.ts Deletes legacy create-library i18n messages.
src/library-authoring/create-legacy-library/index.ts Deletes legacy create-library module export.
src/library-authoring/create-legacy-library/data/apiHooks.ts Deletes legacy create-library mutation hook.
src/library-authoring/create-legacy-library/data/api.ts Deletes legacy create-library API helper.
src/library-authoring/create-legacy-library/CreateLegacyLibrary.tsx Deletes legacy create-library page/component.
src/library-authoring/create-legacy-library/CreateLegacyLibrary.test.tsx Removes tests for deleted legacy create-library flow.
src/index.jsx Removes /libraries-v1/create route and CreateLegacyLibrary import usage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +111 to +112
// Studio home library for legacy libraries
window.open(`${getConfig().STUDIO_BASE_URL}/home_library`);
courseCreatorStatus: COURSE_CREATOR_STATES.granted,
librariesV2Enabled: false,
});
const studioBaseUrl = 'http://localhost:18010';
Comment on lines +141 to +144
const mockWindowOpen = jest.spyOn(window, 'open');
fireEvent.click(createNewLibraryButton);
expect(mockNavigate).toHaveBeenCalledWith('/libraries-v1/create');
expect(mockWindowOpen).toHaveBeenCalledWith(`${studioBaseUrl}/home_library`);
mockWindowOpen.mockRestore();
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

3 participants