feat: Info Sidebar menus [FC-0123]

[ChrisChV]

Description

• Add menus in the info sidebar for:
  • Section
  • Subsection
  • Unit in the course outline
  • Unit in the unit page
  • Components in the unit page
• Which user roles will this change impact? "Course Author".

Supporting information

• Github issue: Sidebar Overflow Menus #2790
• Internal ticket: FAL-4337

Testing instructions

• In the course outline, create a Section > Subsection > Unit > Some components.
• In the course outline, add a Section, Subsection, Unit, and some components from a content library.
• In the course outline, click in the Section Card to open the Section Info Sidebar.
• Test the Menus: Duplicate, Move Up, Move Down, Delete.
• In the Section from the library test the menus: View in Library, Unlink from library.
• In the course outline, click in the Subsection Card to open the Subsection Info Sidebar.
• Test the Menus: Duplicate, Move Up, Move Down, Delete.
• In the Subsection from the library test the menus: View in Library, Unlink from library.
• In the course outline, click in the Unit Card to open the Unit Info Sidebar.
• Test the Menus: Duplicate, Copy to Clipboard, Copy Location Id, Move Up, Move Down, Delete.
• In the Unit from the library test the menus: View in Library, Unlink from library.
• In the unit page, test the Menus in the unit sidebar info: Copy to Clipboard, Copy Location id, Delete.
• Open the unit page for the unit from library, test the menus: View in Library, Unlink from library
• Click in a component to open the component sidebar, test the menus: Duplicate, Copy to Clipboard, Move, Delete.
• Click in a component from library, test the menus: View in Library, Unlink from library.

Other information

N/A

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]

Thanks for the pull request, @ChrisChV!

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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 Report

❌ Patch coverage is 95.82245% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.55%. Comparing base (4d7d91b) to head (685fd31).

Files with missing lines	Patch %	Lines
src/CourseAuthoringContext.tsx	95.45%	4 Missing ⚠️
...it/unit-sidebar/unit-info/ComponentInfoSidebar.tsx	94.73%	3 Missing ⚠️
...se-unit/unit-sidebar/unit-info/UnitInfoSidebar.tsx	93.87%	3 Missing ⚠️
src/library-authoring/history-log/HistoryLog.tsx	0.00%	3 Missing ⚠️
...e/outline-sidebar/info-sidebar/UnitInfoSidebar.tsx	96.36%	2 Missing ⚠️
src/course-unit/xblock-container-iframe/index.tsx	91.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2937      +/-   ##
==========================================
+ Coverage   95.51%   95.55%   +0.04%     
==========================================
  Files        1329     1331       +2     
  Lines       30557    30829     +272     
  Branches     6930     7029      +99     
==========================================
+ Hits        29186    29460     +274     
+ Misses       1303     1302       -1     
+ Partials       68       67       -1     

☔ 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.