-
Notifications
You must be signed in to change notification settings - Fork 8
Introduce courseNavigationBar on header slot #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
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. |
| if (selectedUrl.startsWith('http://') || selectedUrl.startsWith('https://')) { | ||
| const url = new URL(selectedUrl); | ||
| if (url.origin === window.location.origin) { | ||
| navigate(url.pathname + url.search + url.hash); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tried to use navigate as much as possible so we can preserve app state and avoid unneeded full page load
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks for the explanation
114be5d to
a79f6cf
Compare
a79f6cf to
45c11fe
Compare
e883f25 to
4536f10
Compare
| ))} | ||
| </Tabs> | ||
| </div> | ||
| <Slot id="org.openedx.frontend.slot.header.courseNavigationBar.extraContent.v1" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This slot was added because on current learning MFE this nav bar has some extra content related to courseware search
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 |
| @@ -0,0 +1,7 @@ | |||
| .course-tabs-navigation { | |||
| border-bottom: 2px solid rgb(232.5, 229.5, 228); // var(--pgn-color-nav-tabs-base-border-base) | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you remove the variable for a hardcoded color?
maybe you could create a variable something like
$border-base-tabs-color: rgb(232.5, 229.5, 228)
and use that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when i created this PR, design tokens on frontend base wasn't ready, so didn't work, i left the comment to remember that and update it when that was ready
arbrandes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.)
| const { data } = useQuery({ | ||
| queryKey: ['org.openedx.frontend.app.header.course-meta', courseId], | ||
| queryFn: () => getCourseHomeCourseMetadata(courseId), | ||
| retry: 2, | ||
| }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we be handling isLoading and isError from useQuery, maybe with some UI indication that loading is happening?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we do anything like that currently? if it's just for the data for the bar I would expect to show it or not when we get the info, it should be quick enough and prevent extra things to mantain (?)
| }; | ||
|
|
||
| return ( | ||
| <div id="courseTabsNavigation" className={classNames('course-tabs-navigation')}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason we need classNames 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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-instruct#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. |
| @@ -0,0 +1,81 @@ | |||
| import { useQuery } from '@tanstack/react-query'; | |||
| import { Slot, useIntl } from '../../../runtime'; | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if possible make it absolute
| const { data } = useQuery({ | ||
| queryKey: ['org.openedx.frontend.app.header.course-meta', courseId], | ||
| queryFn: () => getCourseHomeCourseMetadata(courseId), | ||
| retry: 2, | ||
| }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we do anything like that currently? if it's just for the data for the bar I would expect to show it or not when we get the info, it should be quick enough and prevent extra things to mantain (?)
| const selectedUrl = tabs.find(tab => tab.slug === eventKey)?.url ?? '/'; | ||
|
|
||
| try { | ||
| if (selectedUrl.startsWith('http://') || selectedUrl.startsWith('https://')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to understand in which case the selectedUrl woudln't have http or https?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a case could be a custom implementation that just points to a route on same domain for example if someone sent /cohorts and with navigate will go to that page 🤔 but not sure if im overcomplicating this
| window.location.href = selectedUrl; | ||
| } | ||
| } else { | ||
| navigate(selectedUrl); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if there's an issue with the URL you are trying to parse why are you navigating to it?
| const courseId = extractCourseId(location.pathname); | ||
|
|
||
| const { data } = useQuery({ | ||
| queryKey: ['org.openedx.frontend.app.header.course-meta', courseId], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this base ID be a constant?
26b19ea to
5681171
Compare
I think it got out of sync because there was extra work that was done in instruct after the decision of just migrating this ones as they were I would say that it makes sense if we wrap this one up with the current changes and as inmediate followup we do the update so this one is more in sync with instruct dash, what do you think @arbrandes ? |
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