Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3.2k
fix: Adddefault_auto_field
to cms/apps.py (#8254)#8258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
* fix: Add `default_auto_field` to cms/apps.py* Add default_autofield to `menus.apss`
sourcery-aibot commentedJun 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Reviewer's GuideThis PR updates the application configurations for the CMS and menus apps by specifying a default primary key field type via the Class diagram for updated AppConfig classes in cms and menus appsclassDiagram class CMSConfig { name = 'cms' verbose_name = _('django CMS') default_auto_field = 'django.db.models.AutoField' ready() } class MenusConfig { name = 'menus' verbose_name = _('django CMS menus system') default_auto_field = 'django.db.models.AutoField' } CMSConfig --|> AppConfig MenusConfig --|> AppConfig File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess yourdashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Hey@fsbraun - I've reviewed your changes - here's some feedback:
- Consider using django.db.models.BigAutoField instead of AutoField to align with Django 3.2+ defaults and avoid future primary key limitations.
- For consistency, add
default_auto_field
to all other CMS-related AppConfig subclasses (e.g. placeholders, plugins). - There’s a typo in the PR description/commit message (“menus.apss”); update it to “menus.apps” for clarity.
Prompt for AI Agents
Please address the comments from this code review:##Overall Comments- Consider using django.db.models.BigAutoField instead of AutoField to align with Django 3.2+ defaults and avoid future primary key limitations.- For consistency, add`default_auto_field` to all other CMS-related AppConfig subclasses (e.g. placeholders, plugins).- There’s a typo in the PR description/commit message (“menus.apss”); update it to “menus.apps” for clarity.
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Uh oh!
There was an error while loading.Please reload this page.
fix: Add
default_auto_field
to cms/apps.pyAdd default_autofield to
menus.apps
Description
Related resources
Checklist
main
Summary by Sourcery
Add
default_auto_field
attribute to the CMS and Menus application configurationsBug Fixes:
default_auto_field = 'django.db.models.AutoField'
inCMSConfig
default_auto_field = 'django.db.models.AutoField'
inMenusConfig