#25262: Better document FlatPage.enable_comments and remove it from default
ModelAdmin
--------------------------------------+------------------------------------
     Reporter:  aaugustin             |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  contrib.flatpages     |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  1                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by timgraham):

 * stage:  Unreviewed => Accepted
 * easy:  0 => 1


Comment:

 From the thread:
  Me: A compromise could be to hide the field in the default ModelAdmin and
 let those who want it to enable it with a custom ModelAdmin. What do you
 think?
  [[BR]]
  Aymeric: That would resolve my problem of “WTF is this field” without
 causing too much headache. We should also put a comment in the source code
 stating that the field is unused but we don’t want to remove it because of
 backwards-compatibility.

--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.976a510d1673fe570d4d96ff009ec97a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to