feat: Dashboard updates to support Pathways

[ChrisChV]

Description

• Creates the PathwayCard
• Extracts some components from CourseCard to be reusable.
• Adds the ENABLE_PATHWAY_PILOT_UI flag.
• Creates a new filter Types.
• Refactors the code to support Pathways in the principal list, with filtering, sorting, and pagination.
• Refactors the code to rename components to Item instead of Course

Supporting information

• Internal ticket: FAL-4375

Testing instructions

• Enable ENABLE_PATHWAY_PILOT_UI
• Add this patch: dev-pathway-list-changes.patch
• Log in as a learner and open the learner dashboard.
• Verify that the pathways are listed in the principal list.
• Verify the badge in the cards.
• Verify that you can sort the list.
• Verify that you can filter the list using the status filter.
• Verify that you can filter the list using the types filter.
• Disable ENABLE_PATHWAY_PILOT_UI
• Verify that the pathways and the types filter are gone.

Notes

• I used Claude Sonet 5 to create tests and it helped me rename the files and folders
• There are parts of PathwayCard that have not been fully implemented because they depend heavily on how the backend is implemented:
  • What banners and footers will the pathways have? The same ones as the courses.
  • What button actions will they have?
  • What access messages will the pathways have? The same ones as the courses?

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @2U-aperture.

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 99.39024% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 98.39%. Comparing base (3ef3185) to head (a8136df).
⚠️ Report is 91 commits behind head on master.

Files with missing lines	Patch %	Lines
...ners/CourseCard/components/CourseHeaderActions.tsx	88.88%	1 Missing ⚠️
src/containers/FilterControls/FilterControls.tsx	94.11%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #860      +/-   ##
==========================================
+ Coverage   98.19%   98.39%   +0.20%     
==========================================
  Files         145      162      +17     
  Lines        1388     1687     +299     
  Branches      297      363      +66     
==========================================
+ Hits         1363     1660     +297     
- Misses         25       27       +2     

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

[navinkarkera]

@ChrisChV Looks good. Found one issue where the types filter is visible even when we set ENABLE_PATHWAY_PILOT_UI=false. Please take a look at the suggestions below.

[ChrisChV]

@navinkarkera Also in 2932921 I refactored the code to use the category naming instead of type

[navinkarkera]

@ChrisChV Thanks! Looks good.

[arbrandes]

Heads up: the frontend-base conversion of Learner Dashboard will in all likelihood land before this PR. (See the announcement.) I apologize for the inconvenience, but once that happens (probably this week), the feature will have to be refactored accordingly.

I suggest not closing this PR, though: once the legacy-mfe branch exists, just change this PR's target to it. However, this means this will automatically become a backport, and a new PR to master will need to be reviewed and merged before this one is considered.

[itsjeyd]

Hey @ChrisChV, if you haven't already could you follow up on Adolfo's comment above and see if this is unblocked for next steps (= if the legacy-mfe branch is available now)?

[itsjeyd]

@ChrisChV Also, since this is part of the Pathways Pilot can we consider it approved from a product perspective? (Asking because I'm not completely sure what the status of that project is in terms of approval for relevant designs.)

[navinkarkera]

@itsjeyd I believe we can consider it approved but @ChrisChV cannot work on it due to changes in the designs and we want to wait for it to be finalized.

[ChrisChV]

cannot work on it due to changes in the designs and we want to wait for it to be finalized.

@itsjeyd Yes, the designs changed after this implementation was completed. I want to wait until they are finished and validated before continuing.

[itsjeyd]

@navinkarkera @ChrisChV OK, thanks for the info. I'll label this as product-review-complete now, and mark it as blocked.