refactor: downstream entity links api [FC-0076]

[navinkarkera]

Description

Refactors downstream links API to handle multiple filters using a single API. Also adds a new route to return summary of library links for a given course.

Useful information to include:

• Which edX user roles will this change impact? Common user roles are "Course Author" and "Developer".

Supporting information

• Part of: Course: Libraries Page: Review Content Updates Tab frontend-app-authoring#1566
• Private-ref: FAL-4007

Also addresses following comments

• feat: entity link view and api #36190 (comment)
• feat: add API to return list of downstream blocks for an upstream [FC-0076] #36253 (comment)

Testing instructions

See openedx/frontend-app-authoring#1699 for instructions

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• If your database migration can't be rolled back easily.

[openedx-webhooks]

Thanks for the pull request, @navinkarkera!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To 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:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[pomegranited]

Works great @navinkarkera , and the renaming makes sense :) One optional nit, but 👍

• I tested this using the test instructions from openedx/frontend-app-authoring#1699
• I read through the code
• I checked for accessibility issues by using my keyboard to navigate
• Includes documentation
• User-facing strings are extracted for translation

[pomegranited]

nit: can't you just do this?

Suggested change

	return Response({
	'next': self.page.next_page_number() if self.page.has_next() else None,
	'previous': self.page.previous_page_number() if self.page.has_previous() else None,
	'count': self.page.paginator.count,
	'num_pages': self.page.paginator.num_pages,
	'current_page': self.page.number,
	'results': data
	})
	return super().get_paginated_response(data, *args, **kwargs)

[navinkarkera]

@pomegranited I wanted to replace next and previous links by page number, but I understand that it was not clear. Updated here: 77cac91

[pomegranited]

Huh ok.. that makes the returned data non-standard for a paginated DRF view, but your update at least makes this clearer.

[navinkarkera]

I wanted to make it work in useInfiniteQuery which expects next or previous page number instead of links.

[ChrisChV]

To keep the standard, maybe instead of replacing next and previous, you can add the page numbers as new values: next_num_page and previous_num_page. What do you think?

[navinkarkera]

@ChrisChV Makes sense, updated.

[ChrisChV]

Looks good! With some nits

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[kdmccormick]

Thanks!