joi-validators

README.md

joi-decorators

What do we want?

Something similar to (roughly, not even syntactically ok):

------
class User {
  @Min(10)
  @Max(10)
  @NotNull
  private _name: string
}
------ or
class User {
  private _name: string

  @Min(10)
  @Max(10)
  @NotNull
  set name (): string {

  }
}

validator = new JoiValidator(...) // <- this is what we want.

user:User = new User(...)

errors:Error = validator.validate(user)

for (let error:Error of errors) {
  console.log(error)
}

We can actually make this much more simple (and powerful):

class User {
    @validate(Joi.string().alphanum().min(3).max(30).required())
    username: string;
    @validate(Joi.string().regex(/^[a-zA-Z0-9]{3,30}$/))
    password: string,
    @validate([Joi.string(), Joi.number()])
    access_token: [string, number],
    @validate(Joi.number().integer().min(1900).max(2013))
    birthyear: number,
    @validate(Joi.string().email())
    email: string;
}

This generates metatada:

[
    { key: "username", val: Joi.string().alphanum().min(3).max(30).required() },
    { key: "password", val: Joi.string().regex(/^[a-zA-Z0-9]{3,30}$/) },
    { key: "access_token", val: [Joi.string(), Joi.number()] },
    { key: "birthyear", val: Joi.number().integer().min(1900).max(2013) },
    { key: "email", val: Joi.string().email() }
]

The real implementation will use a ES6 Map not an array...

The function _createSchemaFromMetadata becomes then very simple 👍

The only missing bit is .with('username', 'birthyear').without('password', 'access_token'); but we I think .required() gets you the same.

Oh, that is a good idea... I've been too long in Java. On that way we support out of the box all the joi constraints and we dont need to make changes if there are new.

Amazing project and can be done in one evening 🤣 TypeScript rules 💯

I can see a problem with it... we are then tied to Joi which it is fine because it is a de-facto standard but we need to compromise on it.