Skip to content

feat: apply ADR standardization to AuthorGrading apis#38726

Open
taimoor-ahmed-1 wants to merge 1 commit into
openedx:feat/axim-api_improvementsfrom
edly-io:feat/author_grading_adr_standardization
Open

feat: apply ADR standardization to AuthorGrading apis#38726
taimoor-ahmed-1 wants to merge 1 commit into
openedx:feat/axim-api_improvementsfrom
edly-io:feat/author_grading_adr_standardization

Conversation

@taimoor-ahmed-1

@taimoor-ahmed-1 taimoor-ahmed-1 commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Description

The FC-0118 initiative introduces a comprehensive standardization of APIs across the platform, guided by 15 newly defined Architectural Decision Records (ADRs). These ADRs collectively establish consistent patterns for serializers, permissions, error handling, pagination, filtering, authentication, versioning, and overall API design. Through this effort, existing endpoints are being refactored and aligned to ensure uniformity, improved developer experience, and long-term maintainability, while also reducing redundancy and inconsistencies across services.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jun 8, 2026
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @taimoor-ahmed-1!

This repository is currently maintained by @openedx/wg-maintenance-openedx-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:

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.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jun 8, 2026
@taimoor-ahmed-1 taimoor-ahmed-1 force-pushed the feat/author_grading_adr_standardization branch from 39a5a99 to 3873eb0 Compare June 10, 2026 06:58
@taimoor-ahmed-1 taimoor-ahmed-1 self-assigned this Jun 10, 2026
@taimoor-ahmed-1 taimoor-ahmed-1 force-pushed the feat/author_grading_adr_standardization branch from 3873eb0 to 2c99e33 Compare June 10, 2026 12:48
@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jun 10, 2026
@taimoor-ahmed-1 taimoor-ahmed-1 force-pushed the feat/author_grading_adr_standardization branch from 2c99e33 to 57c9593 Compare June 10, 2026 12:53
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Jun 10, 2026
from openedx.core.lib.api.mixins import StandardizedErrorMixin

_COURSE_ID_PARAMETER = OpenApiParameter(
name="course_id",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we change course_id param to course_key as its a new versioned API according to this comment and OEP attached on the comment?

@taimoor-ahmed-1 taimoor-ahmed-1 force-pushed the feat/author_grading_adr_standardization branch from 57c9593 to e6775d5 Compare June 10, 2026 14:05
@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jun 10, 2026
Comment on lines +72 to +87
def _resolve_course_key(course_key_string: str) -> CourseKey:
"""
Parse ``course_key_string`` into a ``CourseKey`` and verify the course exists.

Raises ``NotFound`` for both unparseable keys and missing courses, which
the ADR 0029 envelope renders as a structured 404. Replaces the legacy
``@verify_course_exists()`` decorator and avoids relying on
``DeveloperErrorViewMixin``.
"""
try:
course_key = CourseKey.from_string(course_key_string)
except InvalidKeyError as exc:
raise NotFound("The provided course key cannot be parsed.") from exc
if not CourseOverview.course_exists(course_key):
raise NotFound(f"Course {course_key_string} not found.")
return course_key

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

we have this function being added to pull/38708 as well. Can also move common func to utils and handle course_id there as well and change it to course_key.

@mphilbrick211 mphilbrick211 moved this from Needs Triage to In Eng Review in Contributions Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: In Eng Review

Development

Successfully merging this pull request may close these issues.

4 participants