forked from openedx/frontend-component-footer
-
Notifications
You must be signed in to change notification settings - Fork 22
feat: add navigation links to make footer consistent #13
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
Merged
ahmed-arb
merged 17 commits into
edly-io:teak/indigo
from
zubairshakoorarbisoft:zubair/TIA-137-61
Aug 29, 2025
Merged
Changes from 15 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
4e083fd
fix: made footer consistent where using custom footer
84988dc
fix: added LMS footer navlinks
8393f68
fix: linting error fixed and removed unecessary vars
eb2cf3d
fix: code refactoring
0ce52e3
fix: code refactoring
d6f6833
fix: code clean
b764c82
fix: snapshot updated
40fb466
Merge branch 'teak/indigo' into zubair/TIA-137-61
zubairshakoorarbisoft 973e1b8
fix: redundant images removed after conflict resolution
e3ed25f
fix: conflict resolved and snapshot updated
a8ee834
fix: updated footer links according legacy pages
fe2cf7a
fix: code ckean
a339ec0
fix: code clean
c14be31
fix: code clean
c5d04cb
fix: lint errors fixed
4f6b37d
fix: fixed typo
4e78bcc
test: update the test coverage for the footer nav
arbirali File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should there be default links in case the config is not present? Otherwise, it would look like an empty footer.
Uh oh!
There was an error while loading. Please reload this page.
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.
@DawoudSheraz We are getting INDIGO_FOOTER_NAV_LINKS variable from indigo side, if there is any default one, will reflect here otherwise it should be same as legacy pages.
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.
How will it be same as legacy pages?
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.
because
INDIGO_FOOTER_NAV_LINKSis setting from indigo with following command:tutor config save --set "INDIGO_FOOTER_NAV_LINKS=[{"title": "About", "url": "/about"}, {"title": "Contact", "url": "/contact"}]"And we are using that same value here in footer component so that the navlinks on both sides will same.
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.
Let's say you unset the
INDIGO_FOOTER_NAV_LINKSvariable using the following command:tutor config save --unset "INDIGO_FOOTER_NAV_LINKS"When this is done, Tutor automatically sets a default set of 7 footer navigation links for all MFEs. So, if
INDIGO_FOOTER_NAV_LINKSis not explicitly set, Tutor Indigo provides default navlinks across every MFE.The following line sets the default value for
INDIGO_FOOTER_NAV_LINKSin the Tutor config at this path:env/apps/openedx/settings/lms/production.pyTo open this file, first run the following command to locate the Tutor environment root:
This will output the path to your Tutor project. Navigate to that directory and open the file at:
Here, you’ll find where Tutor sets the default footer nav links.
However, if we’re not using Indigo (e.g., using this footer component in another theme or in a standalone setup), we default to an empty array, since the default
edx-platformconfiguration does not include any footer navlinks. You can confirm this in the Footer.jsx source code.