#32954: Improve error message with URLValidator and schemes
-------------------------------------+-------------------------------------
Reporter: tomdjango | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: error message | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
I think using [https://docs.djangoproject.com/en/3.2/ref/models/fields
/#error-messages `error_messages`] is the way forward here.
I don't think we can change the default — too many projects will depend on
that — and I'd guess folks would object that we were leaking unwanted info
if we added extra context here.
What's a Valid URL for the application depends on the validators in play.
Lots and lots and lots of "Valid URLs" (from an RFC perspective) are
already excluded by `URLValidator.schemes`' default value. "Enter a valid
URL." already takes this into account.
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/32954#comment:1>
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/067.b87464b1f9e71a443acd54c220bbdaf5%40djangoproject.com.
