#32523: Warn when trying to use a widget as a field in a form
----------------------------------+--------------------------------------
Reporter: Anders Hovmöller | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Carlton Gibson):
The workflow is pretty standard for OSS project. Discussion happen on the
DevelopersMailingList with the Issue tracker for concrete addressable
items.
This is more or less the only way to keep it maintainable given the volume
of ideas/suggestions/reports.
See the guide on
[https://docs.djangoproject.com/en/3.1/internals/contributing/bugs-and-
features/#requesting-features Requesting features] — it does try to guide
you to the mailing list rather than the issue tracker.
I'm not convinced that a whole new category of checks for forms is worth
the maintenance cost. It may be! But my suggestion was to prototype it,
and then canvas opinion as to whether to push it forwards. It's not just
"if I did this would you take the PR" — we need a consensus that yes, this
is a new group of checks we want to bring into the framework.
--
Ticket URL: <https://code.djangoproject.com/ticket/32523#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.ee1e65980071a3242caff6610653a716%40djangoproject.com.
