| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| |/
| |
| |
| | |
* commit 'b5e545b0e0a3a614562293fd7755cd8d2283e8d2':
Squashed 'json/' changes from ab0b1ae71..20c1bb1d9
|
| |
| |
| |
| |
| |
| |
| | |
20c1bb1d9 test for non-ascii digits in various formats
git-subtree-dir: json
git-subtree-split: 20c1bb1d9ec0d6f995fc06d6ea270d7155ac9d43
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
* commit '6cf6ff85b7cf595609a10267a85d354202e3b2f0':
Squashed 'json/' changes from eb619047f..ab0b1ae71
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ab0b1ae71 fix draft4 schemas
0df96bc38 group tests to avoid duplicating test descriptions
93293efca fix indentation
76b529ff6 Merge pull request #482 from json-schema-org/ether/more-date-time-tests
57f1d63d7 some more tests for "date" and "time" formats
git-subtree-dir: json
git-subtree-split: ab0b1ae710158817af2e48556e22377363aeb169
|
| |
| |
| |
| |
| | |
We don't want to grow the public API of RefResolvers, they
have enough issues already.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Remove shebangs from nonexecutable scripts
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When packaging jsonschema and poetry-core (which bundles it) in Fedora, we have
realised that there are nonexecutable files with a shebang line.
It seems that the primary purpose of these files is to be imported from Python code
and hence the shebangs appear to be unnecessary.
Shebangs are hard to handle when doing downstream packaging, because it makes
sense for upstream to use `#!/usr/bin/env` python while in the RPM package,
we need to avoid that and use a more specific interpreter. Since the
shebangs were unused, I propose to remove them to avoid problems.
|
| | |
|
| |
| |
| |
| | |
Also simplify its implementation, what it's doing is just zip.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's in security fix only mode (till EOY) and doesn't support
module-level __getattr__ yet, which presents enough of a minor
nuisance to drop it.
Users should stick to older jsonschema versions (which should be
properly marked.)
|
| |
| |
| |
| |
| | |
importlib.metadata is in the standard library now, so there's
not much purpose in pre-calculating this attribute.
|
| |
| |
| |
| | |
May as well, this is only used in 2 places.
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
* commit '2591383efc85ba04e52e09aa73376f515baa4a49':
Squashed 'json/' changes from 878b0ad5f..eb619047f
|
| |
| |
| |
| |
| |
| |
| |
| | |
eb619047f Merge pull request #504 from json-schema-org/minContains-0-but-maxContains
c41a68e83 Add tests for minContains = 0 but with maxContains
git-subtree-dir: json
git-subtree-split: eb619047f145de038d60e1ded4b7957d4fe6bd2f
|
| |
| |
| |
| |
| |
| | |
The unevaluated* validators will definitely need rewriting,
what they do right now is completely incorrect (which bugbear
points out at least, though poking at them trivially also does).
|
| |
| |
| |
| |
| |
| |
| | |
Fixes a bug where maxContains was being ignored if minContains was set to 0.
Also now short circuits as soon as more than maxContains is reached rather
than continuing to validate.
|
| |
| |
| |
| |
| |
| | |
Since then, types aren't objects, they're just strings.
This just wastes time catching exceptions for newer drafts.
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
* commit '0fe6d845792049d67e25b452ca056689783358eb':
Squashed 'json/' changes from bb2a20d3e..878b0ad5f
|
| |
| |
| |
| |
| |
| |
| | |
878b0ad5f properly escape this newline character - thanks Srikrishnan Suresh!
git-subtree-dir: json
git-subtree-split: 878b0ad5f016915572dab7a4543a045d38b7098e
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
recursiveRef is broken in the same way dynamicRef is.
|
| |
| |
| |
| |
| |
| |
| | |
This isn't correct, $defs doesn't have behavior (it isn't an assertion).
The reason these tests fail is because the dynamicRef implementation isn't
fully correct (will need some restructuring).
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Saves a bit of work (given test suite schemas are 'guaranteed' to
be valid), but more importantly is easier to debug with a debugger
since there's only one pass of validation for an example.
|
| | |
|
| | |
|
| | |
|