#36131: URL validation redesign and modernization
-------------------------------+-----------------------------------------
     Reporter:  Ludwig Kraatz  |                    Owner:  Ludwig Kraatz
         Type:  New feature    |                   Status:  closed
    Component:  Core (Other)   |                  Version:  dev
     Severity:  Normal         |               Resolution:  wontfix
     Keywords:  URL Validator  |             Triage Stage:  Unreviewed
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  1
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+-----------------------------------------
Changes (by Natalia Bidart):

 * resolution:   => wontfix
 * status:  new => closed
 * summary:  URLValidator not correctly validating URLs => URL validation
     redesign and modernization
 * type:  Bug => New feature
 * version:  5.1 => dev

Comment:

 Hello Ludwig,

 Thank you for your time and commitment in describing your view in this
 ticket. While the `URLValidator` may not align with your expectations in
 naming, it is a functional URL validator, and thousands of services rely
 on its current behavior. Changing this behavior would require a planned
 deprecation path and clear release notes, which is why your request is
 better classified as a new feature request. There is a clear and
 documented[https://docs.djangoproject.com/en/stable/internals/contributing
 /bugs-and-features/#requesting-features procedure to requesting a new
 feature], and I kindly ask that you follow it if you wish to pursue this
 further. Please also note that your project can easily define custom
 validators to your liking and use those in your model and form fields.

 As previously suggested, if you wish to continue discussing your concerns
 in more detail, you can do so on the Django Forum, where a broader
 audience can engage with the topic.

 That being said, I must note that I find the tone of your messages
 somewhat confrontational, and at times the point you are trying to make is
 unclear due to the extensive elaboration. For future discussions in the
 Django Forum I encourage a more focused and concise approach to ensure
 your feedback is more easily understood and leads to a more productive
 conversation.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36131#comment:18>
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 visit 
https://groups.google.com/d/msgid/django-updates/01070194bdfbd837-6106882f-7d09-4624-a074-97ace9b50023-000000%40eu-central-1.amazonses.com.

Reply via email to