These features are pretty core-related.
1. Features from django-polymorphic. To mantain bw compatibility, the
hierarchy parent could need to add something like polymorphic=True in the
meta to this feature be activated.
2. Something like this snippet regarding Inlines in
admin: https://djangosnippets.org/snippets/2032/, to be able to do this:
class A(models.Model):
b = OneToOneField('B')
class B(models.Model):
...
class AInlineAdmin(StackedInline):
model = A
class BAdmin(ModelAdmin):
inlines = (AInlineAdmin)
site.register(B, BAdmin)
Sometimes, doing this could be desirable as it was in my case.
Additionally, I don't know if it is a feature or a bug, but when I see the
inline model section for a O2O field, the section is labeled as:
(verbose_name_plural)
(verbose_name) #1
Example (the Customer model admin has an inline to ContactDetails; the
ContactDetails model has a direct O2O field to Customer; in this case I
didn't use the reverse inline snippet I posted above, but the standard
supported way):
Contacts Details
Contact Details #1
Even when there is only one element (since it is a O2O). Could a change be
done for that case so these captions become...
(verbose_name)
(nothing)
only for the O2O case? (both in the standard way and -if you decide to
support- the inverse inline)
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/a96740fe-c094-401b-82de-891836b6fc8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
