Add support for ajv-keywords

[techntools]

Useful to add custom validations.

I am using it in sequelize-to-openapi

[techntools]

@wesleytodd PTAL

[wesleytodd]

Hey! Can you describe a bit what this does? I am not familiar with the lib so I would like to understand a bit more what this helps folks do before taking on the additional dep.

[wesleytodd]

I am going to mark this as approved since it requires it to run CI for first time contributors, but I still would like to hear more about what this provides functionality wise, and maybe even ask that we write slightly more docs on it since that package doesn't even have a good description in it's readme.

[techntools]

@wesleytodd

Lets say you have a following json schema definition:

{
    type: 'object',
    properties: {
        name: {
            type: 'string',
            pattern: '^[a-zA-Z]$'
        }
    }
}

But json schema does not support flags such as i, g, etc.

With ajv-keywords, you can use custom keyword like regexp to get over that limitation:

{
    type: 'object',
    properties: {
        name: {
            type: 'string',
            regexp: {
                pattern: '^[a-z]$',
                flags: 'i'
            }
        }
    }
}

[wesleytodd]

Ah, interesting and for sure useful. Does this then also hook into the validation so that works correctly? Sorry for the niave questions here, but I think that this would be great to add to your docs if that is something you could do. Also, I think now that I have approved, if you push again it should re-triger the CI.

[techntools]

@wesleytodd

It does participate in the validation

I have added an example as well with validPath()

[techntools]

@wesleytodd

I apologise that your approval got dismissed as I forced pushed to my branch.

Added more test to show that query param can be validated with ajv-keywords

[wesleytodd]

New approval, but I think maybe the GH feature here is broken because what use is it if a new push doesn't start triggering the ci? So if this doesn't work I might go ahead and change the setting on the repo.

[wesleytodd]

I updated the CI, I think if you rebase your PR it might fix the fact that it wont run for you as a new contributor.

[techntools]

@wesleytodd

All checks are passed

Thanks for updating the CI.

Please approve once again.

[wesleytodd]

published as 1.1.0