not null or not empty validation

[Bruno Reis]

For the following:
schema
  {
      "description":"new user registration form",
      "type":"object",
      "properties": {
        "username":    {"type":"string","optional":false},
        "emailaddress":{"type":"string"},
        "password":    {"type":"string"},
        "password2":   {"type":"string"}
      }
    }

I see that
  {
        "username": "",
        "emailaddress": "asdf",
        "password": "asdf",
        "password2": "asdf"
    }

validates Ok

and
  {
        "emailaddress": "asdf",
        "password": "asdf",
        "password2": "asdf"
    }
dont

what I think is a nice behaviour.
But in web, using forms, its very common to validate a "not blank" or "not empty" string.

How should I define that on the schema?

[Kris Zyp]

I think you want:
"username": {"type":"string","minLength":1}
(note that optional defaults to false, so you don't need to set it to false)
Is that sufficient for your use case?
Kris

[Bruno Reis]

That is exactly what I was thinking. Just checking to see if there was another proper way to do that. Thanks.

2008/11/29 Kris Zyp <kri...@gmail.com>