Adding permission checks to subsection and unit sidebar settings

[jacobo-dominguez-wgu]

Description

This PR extends the canEditCourseContent permission gating to the section, subsection, and unit sidebar settings on the course outline page, so that users who can view a course but cannot edit its content see these settings in a read-only state instead of being able to change them.

Added unit tests to support modifications and created new unit tests files to increase code coverage.

User roles impacted

• Course Auditor — will now see section, subsection, and unit sidebar settings in a disabled/read-only state when they lack edit permission.
• Users with full edit permission see no change in behavior.

Supporting information

Addresses comment #3200 (comment)
Coses openedx/openedx-authz#383.
Figma: link

Testing instructions

1. Open a course as a user with canEditCourseContent (any but Course Auditor) . Open the course outline, select a section, subsection, and unit in the sidebar, and confirm all settings (highlights edit, release date, grading, visibility, special exams, prerequisites) are editable as before.
2. Open the same course as a user without canEditCourseContent (Course Auditor). Confirm:
   • The Highlights edit button is hidden, but existing highlights are still shown.
   • Release date/time pickers are read-only.
   • Grading toggle, grader dropdown, due date/time, assessment-results toggles, and special-exam options are disabled.
   • Prerequisite dropdown, min-score / min-completion inputs, and the prerequisite checkbox are disabled.

Other information

View on section sidebar settings without canEditCourseContent permission

View on subsection sidebar settings without canEditCourseContent permission

View on unit sidebar without settings canEditCourseContent permission

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, @jacobo-dominguez-wgu!

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

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.03%. Comparing base (87cba01) to head (3bb0615).

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #3250    +/-   ##
========================================
  Coverage   96.03%   96.03%            
========================================
  Files        1407     1407            
  Lines       34287    34302    +15     
  Branches     7882     8157   +275     
========================================
+ Hits        32928    32943    +15     
  Misses       1318     1318            
  Partials       41       41            

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

[BryanttV]

Hi @jacobo-dominguez-wgu, thanks for handling this! I was testing it and everything works great for subsections and units. However, if I select a course section without Highlights, the 'Add Highlights' button remains enabled for Course Auditors

Can we fix this?

[jacobo-dominguez-wgu]

Hi @jacobo-dominguez-wgu, thanks for handling this! I was testing it and everything works great for subsections and units. However, if I select a course section without Highlights, the 'Add Highlights' button remains enabled for Course Auditors

Can we fix this?

Fixed! Thanks for catching this!

[BryanttV]

LGTM!