Skip to content
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 a POST endpoint for listing courses #35586

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

viadanna
Copy link
Contributor

@viadanna viadanna commented Oct 3, 2024

Description

This pull request introduces functionality to filter courses using a POST request in the course API. The reason for this is to be able to able to use a filter larger than allowed in GET query params.

The key changes include adding a new test for POST request filtering, modifying the get_queryset method to handle POST data, and adding a POST method to the view.

Testing instructions

  1. Make a POST request to /api/courses/v1/courses/ to query for courses.
  2. Ensure the results are the same for the GET request.

Deadline

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

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Oct 3, 2024
@openedx-webhooks
Copy link

openedx-webhooks commented Oct 3, 2024

Thanks for the pull request, @viadanna!

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.


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:

  • 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.

@mphilbrick211 mphilbrick211 added the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Oct 10, 2024
@mphilbrick211
Copy link

Hi @viadanna! Looks like a few additional tests popped up. Can you see if you can run them?

@mphilbrick211 mphilbrick211 removed the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Oct 28, 2024
@viadanna
Copy link
Contributor Author

Sure thing, done @mphilbrick211

@mphilbrick211 mphilbrick211 added the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Nov 4, 2024
@mphilbrick211
Copy link

Apologies, @viadanna - but there's an additional test that needs to be run.

Thank you for your patience. I've put this pull request out to our Core Contributors for review.

@farhaanbukhsh farhaanbukhsh self-requested a review March 13, 2025 10:15
@@ -356,6 +359,12 @@ def get_queryset(self):
mobile_search=form.cleaned_data.get('mobile_search', False),
)

def post(self, request, *args, **kwargs):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you add a docstring here so that the generated OpenAPI/Swagger will have an explanation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @deborahgu, it's the same as the GET endpoint. I've added the POST example to the class docstring, is that good enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @deborahgu, it's the same as the GET endpoint. I've added the POST example to the class docstring, is that good enough?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the class docstring would be fine but I don't see it there -- am I missing it? Just explaining what should be in the payload would be good.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @deborahgu I missed pushing the changes. However, I found an issue with the implementation and will have to re-work it. I'll mark this as a draft for the time being.

@viadanna viadanna self-assigned this Mar 20, 2025
@viadanna viadanna changed the title feat: add a POST endpoint for listing courses draft: feat: add a POST endpoint for listing courses Mar 20, 2025
@farhaanbukhsh farhaanbukhsh changed the title draft: feat: add a POST endpoint for listing courses feat: add a POST endpoint for listing courses Mar 24, 2025
Copy link
Member

@farhaanbukhsh farhaanbukhsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@viadanna I have added one nit but it looks good overall, we should add api documentation so that is shows well in api-docs i.e https://github.com/openedx/edx-platform/blob/master/docs/lms-openapi.yaml

Comment on lines +344 to +347
form = CourseListGetForm(
self.request.data if self.request.method == 'POST' else self.request.query_params,
initial={'requesting_user': self.request.user}
)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

       form_data = self.request.data if self.request.method == 'POST' else self.request.query_params
       form = CourseListGetForm(
            form_data,
            initial={'requesting_user': self.request.user}
        )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs reviewer assigned PR needs to be (re-)assigned a new reviewer open-source-contribution PR author is not from Axim or 2U
Projects
Status: Waiting on Author
Development

Successfully merging this pull request may close these issues.

5 participants