I'm using LGTM to validate REST API inputs and found myself repeating the same validat

Composing chained validations from multiple validators about lgtm HOT 2 CLOSED

square commented on July 22, 2024

Composing chained validations from multiple validators

from lgtm.

Comments (2)

sarus commented on July 22, 2024

So I accomplished this by wrapping LGTM in my own object where I can chain together commonly used parameter validations such as limit, offset, sort etc. to create custom validators.

Looks something like this:

function Validator(){
    this.lgtmValidator = LGTM.validator();
}

Validator.prototype.enabledOnly = function(){
    this.lgtmValidator.validates('enabledOnly')
        .optional()
        .boolean('Must be a boolean');

    return this;
};

Validator.prototype.includes = function(){
    this.lgtmValidator.validates('includes')
        .optional()
        .string('Must be a string')
        .includes(['id', 'username', 'full-name', 'email', 'is-admin', 'enabled', 'last-login'], 
'The "includes" value must be "id", "username", "full_name", "email", or "is_admin"'
        );
    return this;
};

Validator.prototype.build = function(){
    return this.lgtmValidator.build();
}

module.exports = Validator;

Then usage is:

var getUsersValidator = new Validator()
    .enabledOnly()
    .includes()
    .build();

Thanks!

from lgtm.

eventualbuddha commented on July 22, 2024

Your approach seems like a reasonable one. I'm not opposed to adding something in core if it doesn't interfere with the existing flexibility to do what you ended up with. Perhaps changing the behavior of .build() to return distinct objects rather than simply returning the same one over and over again?

from lgtm.

Recommend Projects