#30689: Fix documentation for the `fields` argument of MultiValueField
-------------------------------+--------------------------------------
     Reporter:  Adam Sołtysik  |                    Owner:  nobody
         Type:  Bug            |                   Status:  closed
    Component:  Documentation  |                  Version:  master
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------

Comment (by Adam Sołtysik):

 I get it, though I think there's a difference between a bug when something
 doesn't work, and a "bug" when something works but it maybe shouldn't.
 That's the second time I stumbled upon such a situation -- several days
 ago I was refactoring part of the project because of #30333, and the
 change was also not documented. What's sad is that it's not my fault, as I
 didn't work on the project from the beginning and I didn't write the code
 in question, but now I have no way of being sure whether nothing else is
 broken after the upgrade. So maybe it's worth considering to add a special
 section to release notes just for code-breaking bugfixes ;)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30689#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.87ad3517c83472be945b6ec316a69ed2%40djangoproject.com.

Reply via email to