feat: add PartnerCatalogCourseSerializer #39
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces several improvements to the serializers used in the Corporate Partner Catalog workflow. These changes add new fields, improve nested data responses, and ensure consistent ordering for catalog courses.
✅ Changes Included
1.
PartnerCatalogCourseSerializerImprovementsorder(IntegerField, read-only) mapped fromposition.course_key(SerializerMethodField) exposingcourse_overview.id.ordering = ["position"]insideMetato ensure consistent ordering.2.
PartnerCatalogSerializerUpdatesReplaced
PrimaryKeyRelatedFieldforpartnerwith the fullPartnerSerializerto return nested partner details.Added
stepsusingPartnerCatalogCourseSerializer(many=True, read-only).Introduced new fields:
image = ImageField(read_only=True)email_regexes = ListField(child=CharField(max_length=500))Updated the
fieldsandread_only_fieldslists accordingly.3. General Cleanup
🎯 Motivation