-
Notifications
You must be signed in to change notification settings - Fork 8
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support 'fields' on the ModelAdmin class for non-Page models #6
Comments
Sounds like a good idea. Some of the cases for customizing the modeladmin that I can think of are:
|
Thanks for the input @theju. In regards to custom validation, we at RKH have found that overriding the |
'exclude' behaviour is implemented (as the |
@gasman Hi, Right now I have only 1 solution:
Bu it only hides input instead of removing field panel at all. I need somehow override exclude in Meta. |
Support for However, as per wagtail/rfcs#85, I'm transferring this issue to the wagtail-modeladmin repository. |
This would be reasonably simple to implement into the
modeladmin
app, but it wouldn't be possible right now to pick those panel definitions up in other views, such as for use inInlinePanel
s etc.Maybe this is a discussion for a separate thread, but maybe if we moved toward a django-like approach, where there'd be a central registry of models and their ModelAdmin classes, so configuration like that could be picked up?
I think it would also be sensible to support
fields
andexclude
attributes (maybe using different names?) on the ModelAdmin class. I know our aim isn't to fully support every feature of Django ModelAdmin, and the line must be drawn somewhere, but to save developers from having to import and a bunch of edit handlers and write full definitions, just to change field order or exclude a couple of fields, I think would be a nice feature.Any thoughts?
The text was updated successfully, but these errors were encountered: