-
Notifications
You must be signed in to change notification settings - Fork 356
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Access subschema from error context? #622
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Can you give an example schema where the pointer is inadequate? |
Every schema. The pointer is a pointer for the data structure, not the schema itself. |
Gotcha - I don't think we currently have a mechanism for that. You're welcome to submit a PR that implements it though. Please note that if you do this, performance is a consideration. |
@adjenks would this still be something you would consider following up on? At the moment I'm very happy we are able to cleanup the repo and have revived it. |
@DannyvdSluijs I don't think I have the time right now either unfortunately. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Schemas can have title properties, as well as description. When an error is returned, I would like to get access to the title and possibly also the description field of that subschema where the error was identified. Is this possible? Currently we get the property, pointer, message and constraint. However, in a nested schema, the pointer doesn't really tell you where to look within the schema itself, so it's difficult to recover the descriptive properties, or extended ("x-property") properties, of a schema. Is there a way to access these in the context of an error that I'm just not noticing?
The text was updated successfully, but these errors were encountered: