/api/v2/indicia-publishers//api/v2/indicia-printers//api/v2/brand-groups//api/v2/brands//api/v2/features//api/v2/awards//api/v2/awards/{id}/recipients//api/v2/series-bonds/Each root endpoint includes list/detail serializers, representative filters,
pagination, anonymous read access, conditional request support, OpenAPI schema
coverage, active-only behavior where the model supports soft deletion, and
fixed query-count regression tests.
gcd.0074_series_bond_timestamps adds persistent created and indexed
modified timestamps to Series Bonds. Existing rows use their earliest and
latest approved revision timestamps when those revisions exist. Rows without
approved history receive one shared migration-time value that marks the start
of reliable timestamp tracking.
The local production-copy database had no Series Bond revision rows, so all
6,556 legacy rows received the documented baseline
2026-07-27T20:34:17.981447Z. The migration completed with zero null values.
ruff check apps/api_v2/ruff format --check apps/api_v2/python manage.py checkpython manage.py migrate --checkpython -m pytest apps/api_v2/tests/ -v --tb=short313 passed, 24 existing warnings)200304200304Final EXPLAIN review found the Brand relationship filters, Award recipient
queries, and Series Bond relationship filters using existing indexes. Feature
broad and icontains scans remained acceptable at the observed 47,648-row
scale, so no additional performance migration is included.
https://github.com/GrandComicsDatabase/gcd-django/pull/733
(55 files)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
@gemini-code-assist[bot] commented on this pull request.
This pull request implements Sprint 4 endpoints for the public v2 API, adding read-only viewsets, serializers, filters, and comprehensive tests for Awards, Brand Groups, Brands, Features, Indicia Printers, Indicia Publishers, and Series Bonds. It also introduces a database migration to add and backfill persistent created and modified timestamps for the SeriesBond model. Feedback on the changes suggests utilizing self.get_serializer in AwardViewSet.recipients rather than instantiating AwardRecipientSerializer directly to ensure the serializer receives the proper context.
In apps/api_v2/views/awards.py:
> + page = self.paginate_queryset(filterset.qs) + serializer = AwardRecipientSerializer(page, many=True) + return self.get_paginated_response(serializer.data)
It is recommended to use self.get_serializer instead of instantiating AwardRecipientSerializer directly. Using self.get_serializer ensures that the serializer is initialized with the correct context (such as the request and view), which is important for features like generating absolute URLs or accessing request data within serializer fields.
- page = self.paginate_queryset(filterset.qs) - serializer = AwardRecipientSerializer(page, many=True) - return self.get_paginated_response(serializer.data) + page = self.paginate_queryset(filterset.qs) + serializer = self.get_serializer(page, many=True) + return self.get_paginated_response(serializer.data)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
@DeusExTaco pushed 1 commit.
—
View it on GitHub or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
features will be changed to use feature names, is on beta and in a different branch. I intend to merge that branch to beta soon, then we can see what effect it has one the API ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
features will be changed to use feature names, is on beta and in a different branch. I intend to merge that branch to beta soon, then we can see what effect it has one the API ?
Go ahead and merge it into beta. Once it’s there, I’ll sync the latest beta into PR #733 locally, resolve any conflicts, and run the API tests to see what effect the feature-name changes have. I’ll then push the beta sync to the PR, which should rerun CI without needing an extra change. If everything stays green, the API should be ready to merge into beta. Sound good?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
@jochengcd approved this pull request.
features needs to be touched once we deploy the feature name change
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()