Skip to content

Validation bug? #76

@NivGreenstein

Description

@NivGreenstein

Hey!
We've created the following property:

{
    "type": "number",
    "description": "some description",
    "x-env-value": "ENV_PROP",
    "default": false
}

It passed the package's validation using npm run validation. default: false of course is wrong.
For default false, I think the validation should fail.
What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions