The Wayback Machine - http://web.archive.org/web/20210617002805/https://github.com/topics/jsonschema
Skip to content
#

jsonschema

Here are 173 public repositories matching this topic...

Stranger6667
Stranger6667 commented Apr 29, 2021

When a validation error is reported, it contains only instance_path that points to the erroneous part of the input, but there is no information about what part of the schema caused this error.

The gist of the implementation is to keep a stack of strings while the input schema is compiled. The stack should be convertible to paths::JSONPointer.

The process for regular, non-composite valida

s-knibbs
s-knibbs commented Jun 30, 2019

It seems that the typing module doesn't flatten nested literal type definitions, so the following does not currently work:

SuccessStatus = Literal[200, 201, 204]
ClientError = Literal[404, 401, 403, 409, 400]
ServerError = Literal[500, 504, 503]

@dataclass
class HttpResponse(JsonSchemaMixin):
    status: Literal[SuccessStatus, ClientError, ServerError]
    ...
nirik
nirik commented Apr 12, 2019

Right now the default/docs version of the public consumer just prints out all of each message to stdout. This is nice, but it would be nice if there was something like fedmsg --terse where it just prints out a small subset to give you an idea of the message. This way you can see a lot more info, and can actually run it to watch what all is going on in fedora.

~ fedmsg-tail-3 --terse
[2019-04-1

Improve this page

Add a description, image, and links to the jsonschema topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the jsonschema topic, visit your repo's landing page and select "manage topics."

Learn more