Well, at least in my country there's a law that tells what characters are 
allowed in names, anyway, a single name field would be cool but off topic here: 
"first name" was used here as an example to illustrate that Django projects are 
audited as insecure because there is no input validation at all by default.

For example, django.core.validators does supply a number of useful validators, 
but perhaps it could provide more ie. to restrict special caracters, raise 
warnings for fields which haven't any validators at all and force the user to 
set validators=[] like ForeignKey currently does for on_delete.

Not sure if anything can/should be done though, ideas welcome :)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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-developers/axIVyVbjd0bFateqELjclTklc1vX8cAP7X3nYhjF7OgqXyraSnlBcVZQyIZ74qaTxVWfct410z2Dt8GNU50WE2gPt0f8EYUvKr4fVW_Wlzw%3D%40protonmail.com.
  • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
    • ... Kacper Szmigiel
      • ... Adam Johnson
        • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
        • ... Matthew Pava
          • ... Adam Johnson
        • ... אורי
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
            • ... René Fleschenberg
              • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
    • ... Curtis Maloney
      • ... Florian Apolloner
        • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)

Reply via email to