Skip to content

feat: remove the legacy library viewing and editing page#3080

Open
salman2013 wants to merge 3 commits into
openedx:masterfrom
salman2013:salman/remove-legacy-library-edit-page
Open

feat: remove the legacy library viewing and editing page#3080
salman2013 wants to merge 3 commits into
openedx:masterfrom
salman2013:salman/remove-legacy-library-edit-page

Conversation

@salman2013

Copy link
Copy Markdown
Contributor

Description

Removes the legacy library (V1) tab, routes, and associated UI from Studio Home. The migration wizard (/libraries-v1/migrate) is preserved to allow users to migrate existing legacy library content to V2.

Testing instructions

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'

@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 4, 2026
@openedx-webhooks

openedx-webhooks commented Jun 4, 2026

Copy link
Copy Markdown

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

codecov Bot commented Jun 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.55%. Comparing base (3f531d5) to head (15b1d87).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3080      +/-   ##
==========================================
- Coverage   95.61%   95.55%   -0.07%     
==========================================
  Files        1391     1391              
  Lines       33075    33057      -18     
  Branches     7680     7667      -13     
==========================================
- Hits        31626    31588      -38     
- Misses       1384     1401      +17     
- Partials       65       68       +3     

☔ View full report in Codecov by Harness.
📢 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.

Removes the legacy library (V1) tab, routes, and associated UI from
Studio Home. The migration wizard (/libraries-v1/migrate) is preserved
to allow users to migrate existing legacy library content to V2.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@salman2013 salman2013 force-pushed the salman/remove-legacy-library-edit-page branch from debb76c to dfebf78 Compare June 4, 2026 10:41
@salman2013 salman2013 marked this pull request as ready for review June 4, 2026 10:53
The /libraries-v1 route was removed when the legacy library viewing and
editing page was removed. The migration wizard exit button was still
navigating to that removed route, causing a 404 error.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@irfanuddinahmad irfanuddinahmad requested a review from Copilot June 4, 2026 11:14

Copilot AI left a comment

Copy link
Copy Markdown

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 legacy (v1) libraries experience from Studio Home, leaving only the v2 libraries tab and v2 library creation flow, and updates navigation/tests accordingly.

Changes:

  • Removed the legacy libraries tab, route handling, and related props/state.
  • Updated migration exit navigation to return to the v2 libraries area.
  • Simplified/updated tests to reflect the removal of v1 libraries UI and routes.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
src/studio-home/tabs-section/index.tsx Removes legacy libraries tab/state and simplifies tab routing to v2 libraries only.
src/studio-home/tabs-section/TabsSection.test.tsx Deletes legacy libraries tests and updates navigation expectations to /libraries.
src/studio-home/hooks.tsx Stops exposing librariesV1Enabled from the studio home hook.
src/studio-home/StudioHome.tsx Removes v1 library button logic and always navigates to v2 create page.
src/studio-home/StudioHome.test.tsx Removes tests covering v1-only/v2-only button behavior and legacy create navigation.
src/legacy-libraries-migration/LegacyLibMigrationPage.tsx Changes “Exit” navigation target from /libraries-v1 to /libraries.
src/legacy-libraries-migration/LegacyLibMigrationPage.test.tsx Updates expectation for exit navigation to /libraries.
src/index.jsx Removes /libraries-v1 and /libraries-v1/create routes and legacy create import.

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

Comment thread src/studio-home/tabs-section/index.tsx
Comment thread src/studio-home/tabs-section/index.tsx
Comment thread src/index.jsx
Comment on lines 75 to 79
<Route path="/home" element={<StudioHome />} />
<Route path="/libraries" element={<StudioHome />} />
<Route path="/libraries-v1" element={<StudioHome />} />

<Route path="/libraries-v1/migrate" element={<LegacyLibMigrationPage />} />
<Route path="/libraries-v1/create" element={<CreateLegacyLibrary />} />
<Route path="/library/create" element={<CreateLibrary />} />
Comment thread src/studio-home/tabs-section/TabsSection.test.tsx
Comment thread src/studio-home/StudioHome.tsx Outdated
- Inline librariesV2Enabled directly instead of showV2LibraryURL alias
- Fall back to courses tab in initTabKeyState when librariesV2Enabled is false,
  preventing blank tab when /libraries is visited with libraries disabled
- Add test for librariesV2Enabled: false to prevent regressions

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Jun 4, 2026
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: Waiting on Author

Development

Successfully merging this pull request may close these issues.

4 participants