Introduce courseNavigationBar on header slot#106
Conversation
|
Thanks for the pull request, @diana-villalvazo-wgu! This repository is currently maintained by 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 approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere 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: 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
114be5d to
a79f6cf
Compare
a79f6cf to
45c11fe
Compare
e883f25 to
4536f10
Compare
4536f10 to
26b19ea
Compare
|
@arbrandes do you remember which FWG meeting we discussed this in? I think I need to look through our discussion to remember how the "render conditionally based on role" part is supposed to work (IIRC we talked about apps having roles associated?) |
we discussed it on this one https://openedx.atlassian.net/wiki/spaces/COMM/pages/5255593985/2025-10-09+Frontend+Working+Group+Meeting+Notes+Shai-Hulud+Program+Dashboard+etc For now i didn't introduce anything related to roles and just abstract how is working now (retrieving the enabled tabs from the course-metadata endpoint) |
|
Friendly ping on this, @brian-smith-tcril @arbrandes |
arbrandes
left a comment
There was a problem hiding this comment.
Looks good! I do have some questions and comments, but I think this would work, architecturally speaking. I know we discussed having a way to dynamically assign roles, but we can cross that bridge when we get there.
(Also, sorry it took a while to get here.)
| <div className="nav-menu"> | ||
| <Tabs className="nav-underline-tabs" aria-label={intl.formatMessage(messages.courseMaterial)} onSelect={handleSelectedTab}> | ||
| {tabs.map(({ title, slug }) => ( | ||
| <Tab eventKey={slug} title={title} key={slug} /> |
There was a problem hiding this comment.
I think we might want to use activeKey too, here, no? To give the user indication of which one is active.
|
I also just realized that openedx/frontend-app-instructor-dashboard#32 is not doing the same thing. It's solving a similar problem, though, so we should keep both implementations in sync where it makes sense. |
df88abc to
dbaed01
Compare
arbrandes
left a comment
There was a problem hiding this comment.
A few more questions and suggestions, if you don't mind. Thanks!
1638f0a to
3999521
Compare
|
Hi @diana-villalvazo-wgu! Is this PR still in progress? |
36d94e2 to
d7623b9
Compare
d7623b9 to
de6fc4e
Compare
| @@ -0,0 +1,7 @@ | |||
| .course-tabs-navigation { | |||
| border-bottom: 2px solid var(--pgn-color-nav-tabs-base-border-base); | |||
There was a problem hiding this comment.
styles needed if we want to keep the underline for the whole page and not only for the extension on the tabs
* feat: add `provides` field to App for inter-app data sharing Add a generic mechanism for apps to share data with each other without requiring changes to the App type for each new use case. Includes ADR 0013 documenting the design rationale. Co-Authored-By: Claude <noreply@anthropic.com> * refactor: use `provides` for course navigation bar Replace hardcoded role list with dynamic `provides` lookup. The slot condition now uses a callback that checks registered apps' URL patterns. Tab links use `Link` for client routes and `<a href>` for external ones. Co-Authored-By: Claude <noreply@anthropic.com> * fix: type raw API response and remove dead isMasquerading Co-Authored-By: Claude <noreply@anthropic.com> * refactor: use find-based SCSS copy in Makefile Co-Authored-By: Claude <noreply@anthropic.com> * fix: resolve circular dependency between app.tsx and utils.ts Co-Authored-By: Claude <noreply@anthropic.com> * refactor: use roles instead of URL patterns in provides Apps now provide role names instead of regex patterns. The header derives route paths from roles via getUrlByRouteRole, avoiding duplication of URL knowledge. Co-Authored-By: Claude <noreply@anthropic.com> * refactor: use matchPath for tab and route matching, add tests Replace manual prefix matching with react-router's matchPath in both getActiveTabId and isClientRoute. Add component tests for CourseTabsNavigation and unit tests for utils. Co-Authored-By: Claude <noreply@anthropic.com> * refactor: allow any namespaced ID as provides key The provides key is not limited to app IDs - any namespaced identifier in the ecosystem (slot, widget, etc.) can be used. The course navigation bar now uses its widget ID. ADR updated to reflect this and document rejected alternatives. Co-Authored-By: Claude <noreply@anthropic.com> * refactor: use dedicated provides key, not existing IDs Provides keys should be their own namespaced identifiers so the data can be consumed by any entity independently. Co-Authored-By: Claude <noreply@anthropic.com> * fix: lint error in CourseTabsNavigation test Co-Authored-By: Claude <noreply@anthropic.com> * docs: fix ADR wording * fix: decouple getProvidedData from app ID references Rename parameter to 'key', update JSDoc, and align tests with the convention that provides keys are their own namespaced identifiers. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
b4c9312 to
82c6761
Compare
|
🎉 This PR is included in version 1.0.0-alpha.23 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
As part of the conversion of MFEs to frontend base, we figured it out that 3 different repos will need Course Navigation Bar (Learning, Discussions and Instructor), so instead of having repetitive code on 3 different repos we come up with the following approach:
Screenshot
Tested with template site and instructor dashboard: