General course info card created

[jacobo-dominguez-wgu]

Description

Adding the general course info card, the components for the card were created and also the rect query hook to fetch the required data.
The unit test were created with the assistance of github copilot and supervised to ensure they work well and are useful.

It closes #24
Figma design: https://www.figma.com/design/RnkfsNvyutLkSDXEhEOkEY/Instructor-Experience?node-id=18416-125046&t=Puj6PbVLRMXDgVDK-0

It depends on: openedx/openedx-platform#37588

Warning

There is a field for course run missing on the api response, added a comment here to notify it openedx/openedx-platform#37465 (comment). If the field is missing a NOT SET fallback message is shown

Screenshot

LOADED:

LOADING:

How to test it

• Make sure you have this API endpoint on your local edx-platform feat: Instructor course information v2 apis openedx-platform#37588
• Create a frontend plugin to patch CORS_ORIGIN_WHITELIST, LOGIN_REDIRECT_WHITELIST and CSRF_TRUSTED_ORIGINS with the mfe url (currently http://apps.local.openedx.io:8080)
• npm install && npm run dev
• Go to instructor/course_info

[openedx-webhooks]

Thanks for the pull request, @jacobo-dominguez-wgu!

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

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.45455% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.94%. Comparing base (5b0d465) to head (8089753).
⚠️ Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
...components/generalCourseInfo/GeneralCourseInfo.tsx	95.45%	1 Missing ⚠️
src/providers/QueryProvider.tsx	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            main      #61       +/-   ##
==========================================
+ Coverage   0.00%   78.94%   +78.94%     
==========================================
  Files          5       14        +9     
  Lines          7       57       +50     
  Branches       0       17       +17     
==========================================
+ Hits           0       45       +45     
- Misses         7       12        +5     

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

[diana-villalvazo-wgu]

can you rebase main please? 😄

[diana-villalvazo-wgu]

LGTM! 🚀

[jesusbalderramawgu]

LGTM!

[rodmgwgu]

[nit] Shouldn't we avoid this kind of imports in favor of something like @src/...? Like it's done in frontend-authoring? here is an example: https://github.com/openedx/frontend-app-authoring/blob/master/src/authz/data/apiHooks.ts#L2

[jacobo-dominguez-wgu]

Yes, but we have not set the alias settings yet. I tried doing the same than in authoring but it did not work so maybe there is an issue in frontend-base related to it. We need to create a ticket to address it.

[rodmgwgu]

Could you create the ticket please? thanks!

[jacobo-dominguez-wgu]

Here is the ticket #76

[rodmgwgu]

Looks good, thanks!

[diana-villalvazo-wgu]

with the updates on base branch it seems :courseId is duplicated here