Skip to content

Valid schema is raised as Error toward it should at minimum set as warning (required statement #689

@LasneF

Description

@LasneF

Given a valid schema

type: object
required : ["field2']
properties:
field:
type string

despite field2 is not part of the object this construction is valid (and some time used in synch with schema composition)

the given error

.\component-descriptor.yml:1877:7
error | required field status is not defined in properties oas-schema-check | Schemas | $.paths['/report-jobs'].get.responses['200'].content[

to me default rules for Error should be only for invalid schema / OAS , but not to 'preference or syle' this one should be a warning (at max)

Jsonschema is hard :(

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions