-
Notifications
You must be signed in to change notification settings - Fork 59
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
fix: replace the header with openedx header #327
base: master
Are you sure you want to change the base?
Conversation
ec9abb1
to
418657e
Compare
22d3398
to
977a0a8
Compare
977a0a8
to
a8274a8
Compare
e9e5ac9
to
b65f44f
Compare
content: formatMessage(messages.dashboardPersonal), | ||
isActive: true, | ||
}, | ||
...(!_.isEmpty(dashboard) ? [{ |
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 should keep the condition same as it is in learner-dashboard !!dashboard
.
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.
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 will let the relevant team comment on this.
5fafc13
to
7931d32
Compare
Hey @ahtesham-quraish , I'll be looking over this PR tomorrow! A question that I do have is whether it's possible to move the edX logic of |
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 is great in general - thanks! I'd like to see some of the business-specific code moved elsewhere, though, if we can manage it.
}, | ||
], | ||
userMenu: [ | ||
...(getConfig().ENABLE_EDX_PERSONAL_DASHBOARD ? [ |
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.
Ideally, this should be moved somewhere else. We can either put the header behind a <PluginSlot />
so this 2U-specific can go in a plugin, or, as @jsnwesson comments, this could move to frontend-component-header-edx
.
{ | ||
heading: '', | ||
items: [ | ||
...(_.isEmpty(dashboard) && getConfig().CAREER_LINK_URL ? [{ |
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 also looks like org-specific code that we could take this opportunity to move to a plugin or a header fork.
We were going with feature parity but after looking at the @arbrandes comment we are going to see the strategy to remove the 2u specific code from Dashboard MFE and move it in header-edx fork so that is why we are holding this PR back. |
Description: Replace the header with openedx header van-1914
cf00664
to
c73f946
Compare
c73f946
to
fb35614
Compare
Hi @jsnwesson, we have extracted the edX-specific code out of the learner-dashboard and now using plugin slots to insert that menu. Could you please look at this PR and the following related PRs as well? |
Hi @arbrandes, Thanks. We have removed the business-specific code from the PR. that code will be added through plugin slots in |
Description:
Replace the custom header with the Openedx header using the configurable header and plugin slots
Dashboards
user menu group andCareer
user menu item) is inserted via pluginsJira Ticket
VAN-1951
How this has been tested?
Screenshots