-
Notifications
You must be signed in to change notification settings - Fork 719
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
My downloads page #10137
My downloads page #10137
Conversation
19baeb9
to
e291161
Compare
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 for now, this can live as an additional single page app within the learn plugin (which will mostly just involve moving stuff from where you have it into Learn, and adding a sub-route for the my-downloads SPA to learn).
My reasoning for this is that while this is a separate single page app from Learn, with a separate side nav item, it is entirely dependent on learn, as that's the only place you can initiate downloads from.
...ri/plugins/my_downloads/assets/src/views/DownloadsList/PaginatedListContainerWithBackend.vue
Outdated
Show resolved
Hide resolved
e291161
to
bd98999
Compare
Build Artifacts
|
07214fc
to
acb6151
Compare
acb6151
to
7cbc6b7
Compare
@@ -47,6 +47,29 @@ export default function useContentLink(store) { | |||
return _makeLink(id, isResource, query); | |||
} | |||
|
|||
function genExternalContentURLBackLinkCurrentPage(id) { |
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.
Didnt find a better solution for getting the url of the content renderer to move from my_downloads to learn :/. Due to the fact that they are differents SPA they dont have the same router object
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 seems tractable, if a little complex. Another option here would be to create a content preview page within the downloads SPA, but this can work for now, especially as they both live in the same plugin, so cannot be deactivated separately.
It's possible that some of the work that @marcellamaki is doing in her app bar PR could be reused here to simplify this slightly.
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.
Yes, we may be able to repurpose that here, and once this is merged, I can also do a follow up to change the side navigation item to match the new CoreMenuOption
API @rtibbles
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 @AlexVelezLl ! Nice work.
I think this piece is ready to merge. Can you create a follow up issue that tracks the additional pieces that are remaining to get this working, once the API is ready, and not mocked? (code cleanup of dummy data, API, filtering using the API endpoint for the paginated list containers, etc.) Let me know if you have questions and we can go over it together.
@@ -47,6 +47,29 @@ export default function useContentLink(store) { | |||
return _makeLink(id, isResource, query); | |||
} | |||
|
|||
function genExternalContentURLBackLinkCurrentPage(id) { |
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.
Yes, we may be able to repurpose that here, and once this is merged, I can also do a follow up to change the side navigation item to match the new CoreMenuOption
API @rtibbles
Summary
New my downloads page.
Preview:
Screen.Recording.2023-03-17.at.07.25.45.mov
References
Specs in #9861
Reviewer guidance
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)