René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Validation of required fields inconsistent","articleBody":"The validation of the `required` keyword does not make sense as it is implemented right now, IMHO.\r\n\r\n1. It really does not make any sense to list properties in `required` that do not exist.\r\n2. If you want to use it with `allOf` and therefore have properties in `required` that do not exist, there are already precautions (#154).\r\n3. Currently, there is no validation error in the standard case but as soon as I have `allOf` in my schema, there is a validation error. That is inconsistent. The PR that breaks it: #312\r\n4. In `$ref`erenced schemas, the validation does not take effect either.\r\n\r\nOne of the main reasons why this should urgently be validated (as was in version 0.7.0) is that validators (that use the specification to validate requests/responses) will fail if there is e.g. a typo in one of the entries in `required`. And now there is no way to detect that.\r\n\r\nIn general, the OpenAPI/JsonSchema specification is quite relaxed. If only the bare minimum should be validated, this is probably not the only validation that can basically be removed completely.\r\n\r\nMy take on this:\r\n\r\n1. Best case: Throw validation errors for things that are obvious errors (like specifying a field as required that does not even exist).\r\n2. Second best option: make it configurable (\"strict mode\") or filterable (error IDs to exclude, filter levels, ...).\r\n3. Absolutely necessary minium: make it consistent.\r\n\r\nI'd be willing to provide a PR. But since this has been going [back ](#97) and [forth](#266) I'd like a decision first, where this is going.","author":{"url":"https://github.com/Archelyst","@type":"Person","name":"Archelyst"},"datePublished":"2024-08-09T11:01:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/373/openapi-spec-validator/issues/373"}