-
Updated
May 31, 2021 - JavaScript
jsonschema
Here are 173 public repositories matching this topic...
-
Updated
Jun 12, 2021 - C++
-
Updated
Feb 25, 2021 - Go
-
Updated
Jun 14, 2021 - Python
-
Updated
Dec 1, 2017 - Python
-
Updated
Jun 15, 2021 - Python
-
Updated
Jun 10, 2021 - Python
-
Updated
Jun 14, 2021 - TypeScript
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]
...-
Updated
May 20, 2021 - JavaScript
-
Updated
Sep 26, 2017 - JavaScript
-
Updated
May 25, 2021 - JavaScript
-
Updated
Jun 16, 2021 - TypeScript
-
Updated
Jun 3, 2021 - Java
first issue
留贴为证
-
Updated
Apr 17, 2021 - TypeScript
-
Updated
Jun 16, 2021 - JavaScript
-
Updated
Jun 9, 2021 - TypeScript
--terse support
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
-
Updated
Aug 11, 2020 - TypeScript
-
Updated
Sep 27, 2018 - Vue
-
Updated
Jun 1, 2021 - Python
-
Updated
Jun 15, 2021 - Python
-
Updated
Nov 1, 2017 - JavaScript
-
Updated
May 21, 2020 - Python
-
Updated
Jun 4, 2020 - JavaScript
-
Updated
Jun 3, 2021 - TypeScript
Improve this page
Add a description, image, and links to the jsonschema topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the jsonschema topic, visit your repo's landing page and select "manage topics."
When a validation error is reported, it contains only
instance_paththat 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