Add course nav provides

[diana-villalvazo-wgu]

Description

In order to frontend base provide Course Navigation Bar to our Instructor Dashboard MFE we need to add the proper config so it can be enabled.

Supporting Information

Related PR: openedx/frontend-base#106
Closes #22

Screenshot

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).
• Deprecated propTypes, defaultProps, and injectIntl patterns are not used in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• 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.
• Imports avoid using ../. 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, @diana-villalvazo-wgu!

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

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 81.89%. Comparing base (bcb6d42) to head (02c88e7).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #148   +/-   ##
=======================================
  Coverage   81.89%   81.89%           
=======================================
  Files          87       87           
  Lines        1121     1121           
  Branches      252      240   -12     
=======================================
  Hits          918      918           
- Misses        196      198    +2     
+ Partials        7        5    -2     

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

[arbrandes]

Yes, that last frontend-base version comes with the new i18n stuff, already. :)

[diana-villalvazo-wgu]

Yes, that last frontend-base version comes with the new i18n stuff, already. :)

great, so its ok if i delete my i18/index file right?

[brian-smith-tcril]

great, so its ok if i delete my i18/index file right?

Not quite. The src/i18n/index.ts file in frontend-app repos should follow https://github.com/openedx/frontend-base/blob/main/docs/how_tos/migrate-frontend-app.md#i18n

That will ensure when you run npm run dev the "site version" of the app (that uses site.config.dev.tsx) will work as expected with pulling translations from the openedx-translations repo.

[diana-villalvazo-wgu]

great, so its ok if i delete my i18/index file right?

Not quite. The src/i18n/index.ts file in frontend-app repos should follow https://github.com/openedx/frontend-base/blob/main/docs/how_tos/migrate-frontend-app.md#i18n

That will ensure when you run npm run dev the "site version" of the app (that uses site.config.dev.tsx) will work as expected with pulling translations from the openedx-translations repo.

thanks Brian! i follow your PR and the Readme instructions 👍

[brian-smith-tcril]

The i18n parts all look right to me!

[openedx-semantic-release-bot]

🎉 This PR is included in version 1.0.0-alpha.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀