[ChrisChV]

Description

Review these commits: https://github.com/openedx/frontend-app-learning/pull/2230/changes/fc95bb5db39c19db61db74382352babfbbece639..8bcd114d125127a2b81d1e72be2fd4acacff4dc6

Adds the Progress and Achievements tabs of the pathway pages.

Progress tab

• Completion card with a donut showing the completed items of the pathway.
• Grades table with the progress, pass grade and current grade of each item, and a link to its details.
• Side card that links to the Achievements tab, or says that none have been earned yet.
• PathwayProgressRing: a reusable SVG ring, used by both the donut and the grades table.

Achievements tab

• Grid of certificate cards. The certificate of the pathway itself is highlighted.

Supporting information

• Depends on: feat: Pathways strip in course pages [FC-0137] #2159
• GitHub issue: Pathways Progress & Achievements #2166
• Figma: https://www.figma.com/design/JlEMcenU1JwPsFTHAHDwR3/Pathways?node-id=2272-12444&t=RwdsIxTYgqpOsO0O-4
• Internal ticket: FAL-4398

Testing Instructions

• Review these commits: https://github.com/openedx/frontend-app-learning/pull/2230/changes/fc95bb5db39c19db61db74382352babfbbece639..8bcd114d125127a2b81d1e72be2fd4acacff4dc6
• Apply this patch: dev-pathway-dummy-data.patch.
• Go to the pathway progress page: http://apps.local.openedx.io:2000/learning/pathway/id/progress
• Verify that the page matches the design.
• Go to the achievements page: http://apps.local.openedx.io:2000/learning/pathway/id/achievements
• Verify that the page matches the design.
• Navigate between the pages using the tabs.
• Revert the patch and apply this one: dev-pathway-no-achievements-dummy-data.patch
• Go to the progress page and verify the new state of the achievements note sidebar

Notes

• TODO: The backend still needs to be connected once it's ready.
• TODO: It's missing the empty state of the achievements page. Waiting for a response.
• I used Claude Opus 5.5 to review my code and create tests.

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @openedx/committers-frontend-app-learning.

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 96.81529% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.18%. Comparing base (230799e) to head (8bcd114).

Files with missing lines	Patch %	Lines
src/pathways/PathwayOutline.tsx	0.00%	7 Missing ⚠️
src/pathways/data/api.ts	57.14%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2230      +/-   ##
==========================================
+ Coverage   96.16%   96.18%   +0.02%     
==========================================
  Files         368      398      +30     
  Lines        6019     6315     +296     
  Branches     1486     1531      +45     
==========================================
+ Hits         5788     6074     +286     
- Misses        222      232      +10     
  Partials        9        9              

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

[itsjeyd]

Hey @ChrisChV, if is this part of FC-0137 could you please add that reference to the PR title?

Also, what will we need to do with this in terms of product review? Have the corresponding designs been approved already?