Fix mypy relation resolution in CI
All checks were successful
CI / nightly-e2e (pull_request) Has been skipped
CI / deploy (pull_request) Has been skipped
CI / pr-e2e (pull_request) Successful in 1m16s
CI / ci (pull_request) Successful in 1m23s

Disable reverse manager generation on ArticlePage.category and switch category selection to id-based queries so CI mypy can resolve models reliably.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Mark
2026-03-03 11:37:20 +00:00
parent 7669a5049c
commit f7ca4bc44b
2 changed files with 10 additions and 9 deletions

View File

@@ -68,7 +68,7 @@ class Migration(migrations.Migration):
blank=True,
null=True,
on_delete=django.db.models.deletion.PROTECT,
related_name="articles",
related_name="+",
to="blog.category",
),
),
@@ -79,7 +79,7 @@ class Migration(migrations.Migration):
name="category",
field=models.ForeignKey(
on_delete=django.db.models.deletion.PROTECT,
related_name="articles",
related_name="+",
to="blog.category",
),
),