Skip to content

Conversation

@JohananOppongAmoateng
Copy link
Contributor

Added a warning to the docs warning users about renaming superclass which causes migration problems

Closes #396

@codecov
Copy link

codecov bot commented Dec 26, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.91%. Comparing base (139db51) to head (7c377e4).
⚠️ Report is 24 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #764   +/-   ##
=======================================
  Coverage   82.91%   82.91%           
=======================================
  Files          26       26           
  Lines        1580     1580           
  Branches      250      250           
=======================================
  Hits         1310     1310           
  Misses        206      206           
  Partials       64       64           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@JohananOppongAmoateng JohananOppongAmoateng self-assigned this Dec 29, 2025
@bckohan
Copy link
Collaborator

bckohan commented Jan 5, 2026

This is an upstream issue with Django, outside of our purview to document or fix. I converted #396 to Q&A and answered it.

@bckohan bckohan closed this Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Renaming superclass causes migrations to produce invalid SQL

2 participants