generated from openedx/frontend-template-application
-
Notifications
You must be signed in to change notification settings - Fork 16
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: add authenticatedpageroute so learner can create a shared record link #187
Merged
Merged
Changes from 1 commit
Commits
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 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.
I was under the impression that the
AuthenticatedPageRoute
component was actually a react-routerRoute
of its own. This is indicated in the docs, HOWEVER, the implementation used infrontend-platform
test files just uses it as a wrapper (like this PR does).When digging into the code, I don't see anywhere that
AuthenticatedPageRoute
would ever return an actualRoute
component. See the code in frontend-platform.What's strange is that there ARE implementations where MFEs are adding props like
path
andcomponent
to theAuthenticatedPageRoute
component. See here in frontend-app-learner-portal-enterprise.All of this to say, this PR is clearly fine but I'm also clearly a little confused so will be bringing this to fedX group to hopefully get some clarification on how this component is intended to be used.
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.
Hey thanks for bringing in all of these PR examples! Very valid point in terms of implementation. Originally I did try replacing the
Route
element with aAuthenticatedPageRoute
, but then an error appeared:[AuthenticatedPageRoute] is not a <Route> component. All component children of <Routes> must be a <Route> or <React.Fragment>
This must be a hard requirement for frontend-platform v5, and previous PRs might need to be updated to reflect this rule.
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.
One other thing to note is that the comments in the docs is from 4 years ago (found via git blame), so it should be updated to better represent its implementation.
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.
And lastly, it looks like the implementation in
frontend-app-learner-portal-enterprise
has placed the routes directly intoApp.jsx
(and not wrapped with aRoutes
element), and this was done over two years ago. And they're still usingfrontend-platform v4
.So from that, I think that
AuthenticatedPageRoute
once had served as a substitute forRoute
, but it no longer does in v5.