fix: make schemaPath optional in open api spec#185
Merged
testower merged 2 commits intoMobilityData:masterfrom Nov 6, 2025
Merged
fix: make schemaPath optional in open api spec#185testower merged 2 commits intoMobilityData:masterfrom
testower merged 2 commits intoMobilityData:masterfrom
Conversation
Alessandro100
approved these changes
Nov 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #184
The validator engine is not always able to point to a specific location in the schema for a given error. This seems to be the case for allOf, anyOf and oneOf validations as well as enums. The reason presumably being that there are multiple locations to choose from.
This PR makes the field in the api response nullable, so that consumers can handle that it sometimes comes back as null.