Changes between Initial Version and Version 12 of Ticket #34388


Ignore:
Timestamp:
Mar 10, 2023, 12:49:54 PM (19 months ago)
Author:
T. Franzel
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34388

    • Property Cc David Wobrock Adam Johnson added
    • Property Triage Stage Unreviewed → Accepted

  • Ticket #34388 – Description

    initial v12  
    77    - I really can't come up with a scenario where a user would want a different behavior or rather that a user would be surprised by the implicit resolution.
    88
    9 2. By forcing the user to expand the `Choices` class manually, essentially all meta information is lost. Downstream packages may benefit from this lost information.
    10    - Specifically, as maintainer of [https://github.com/tfranzel/drf-spectacular drf-spectcular] (OpenAPI generator for DRF), I am interested in the name of the choice set (e.g. Suit, Vehicle, Gender) and potentially also the docstring. This would greatly improve OpenAPI generation of choice sets and take out the unnecessary guesswork to find a proper name. (And if anyone wonders, the model field name is not a good candidate for a choice set name.)
     9~~2. By forcing the user to expand the `Choices` class manually, essentially all meta information is lost. Downstream packages may benefit from this lost information.~~
     10   - ~~Specifically, as maintainer of [https://github.com/tfranzel/drf-spectacular drf-spectcular] (OpenAPI generator for DRF), I am interested in the name of the choice set (e.g. Suit, Vehicle, Gender) and potentially also the docstring. This would greatly improve OpenAPI generation of choice sets and take out the unnecessary guesswork to find a proper name. (And if anyone wonders, the model field name is not a good candidate for a choice set name.)~~
    1111 
    1212This PR allows to use `Choices` classes directly as argument, while being transparent. No behavioral changes otherwise.
Back to Top