-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat: add API to return list of downstream blocks for an upstream [FC-0076] #36253
feat: add API to return list of downstream blocks for an upstream [FC-0076] #36253
Conversation
Thanks for the pull request, @rpenido! 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. Where 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. |
c7ed62d
to
3738603
Compare
4516aa2
to
88e9b08
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.
@rpenido Works as expected, just left some suggestions.
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. Only one nit
fcdad4c
to
965e99a
Compare
...djangoapps/contentstore/migrations/0010_publishableentitylink_downstream_parent_usage_key.py
Outdated
Show resolved
Hide resolved
c320186
to
c752f6d
Compare
e92aa0f
to
c8bbff9
Compare
e904b0a
to
537d374
Compare
537d374
to
9bf84b2
Compare
downstream_usage_key_str_list = [str(usage_key) for usage_key in downstream_usage_key_list] | ||
|
||
return Response(downstream_usage_key_str_list) |
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.
NIT: Instead of manually doing this, we can use serializer.
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 avoided it because I was returning only a list of strings.
I updated to use a serializer here (439bc0f) so we can extend it further in the future if needed.
if cur_block.scope_ids.block_type not in ["chapter", "sequential"]: | ||
parent_data["url"] = ( | ||
reverse_course_url("course_handler", cur_block.context_key) + | ||
reverse_usage_url("container_handler", cur_block.usage_key) | ||
) | ||
else: | ||
parent_data["url"] = reverse_course_url("course_handler", cur_block.context_key) |
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.
Not sure if we need to include this data in index as it can be easily derived from the information already present.
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.
You're right. Initially, I thought this would help us handle different waffle flags (like contentstore.new_studio_mfe.use_new_unit_page
) but that is not the case.
Reverted here: 6b27c09
fb6303c
to
439bc0f
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.
@rpenido Looks good, thanks for your patience. 👍
- I tested this: (Tested api via frontend)
- I read through the code
- I checked for accessibility issues
- Includes documentation
439bc0f
to
ff81e48
Compare
Building off the feedback I gave @navinkarkera on #36190, I think that a better API structure would be:
Since both these API endpoints return one entry per downstream item, it makes sense for them to be under Definitely merge this PR now in order to unblock your team! But, please coordinate with @navinkarkera to make a followup PR with this new API structure. |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
This PR adds the api for listing downstream contexts and parents for a given publishable entity.
Additional Information
Testing Instructions
Private ref: FAL-4005