| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
The warnings module still leaves what to be desired vis a vis
cleaning up state, but everything at least passes this way now,
and this removes a testing dependency.
|
|
|
|
|
| |
Other things (the install :/) are just too noisy themselves,
and raise errors.
|
|\
| |
| | |
Add release note about dropping support for Py 3.6
|
| |
| |
| |
| | |
for more information, see https://pre-commit.ci
|
|/
|
| |
It was dropped in https://github.com/Julian/jsonschema/commit/3fb0576411701b57899cf9c812e32046ddc2adf9
|
| |
|
| |
|
|\
| |
| |
| |
| | |
* dependentSchemas-fix:
validators: Fix dependentSchemas when instance is not an object
|
| |
| |
| |
| |
| |
| |
| | |
Just like 'dependentRequired' and 'dependencies', 'dependentSchemas'
needs to handle instance not being an object.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|\ \
| | |
| | |
| | |
| | | |
* commit 'ddef3b4a06be6f66dc1384e31a408ee7658bac1a':
Squashed 'json/' changes from ba3a90534..329efe59c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
329efe59c Update the language around coverage, draft2020-12 is just as usable :)
068131278 Ensure dependentSchemas also properly ignores non-object instances.
git-subtree-dir: json
git-subtree-split: 329efe59c65ea9f49af9c5c07dd6f5d22cb67ef4
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '4ecbea58e0828696f7714abba624e2160518fddd':
Squashed 'json/' changes from 54440eab4..ba3a90534
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ba3a90534 Merge pull request #523 from olegshtch/extendible-schema-test-suite
458e7ac1e Add test suite to test dynamic reference and anchor link and their independency of order
fe405a119 draft/future -> draft/next in $refs also
3d9d35a2a Merge pull request #522 from json-schema-org/ether/draft-next
11b5076f0 rename draft-future to draft-next
0245dcc94 Merge pull request #521 from olegshtch/add-recursive-ref-test-suite
e9fb9cf45 Merge pull request #517 from ChALkeR/chalker/date-time-leap
f1b230c69 Add test from Appendix C. Example of recursive schema extension of the draft.
bb2e37317 Test date-time with leap second on a wrong hour/minute
8b797cfe6 Merge pull request #520 from json-schema-org/ether/custom-dialect
5d23f3112 Add tests for invalid date-time past leap second
63f8e93c1 Improve leap seconds test in optional/format/date-time
3d00f593d test the use of the $vocabulary keyword in a custom metaschema
git-subtree-dir: json
git-subtree-split: ba3a9053400dd6237aef9cc63601758b1d266818
|
|\ \ \
| | | |
| | | | |
Fix prefixItems index reporting in ValidationError
|
|/ / / |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
and
https://github.blog/2021-10-04-beta-github-releases-improving-release-experience/
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit 'cf886386cc0996df6743b425f74675a6d8a1a9ca':
Squashed 'json/' changes from 20c1bb1d9..54440eab4
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
54440eab4 Merge pull request #516 from ChALkeR/chalker/ipv6
e7b22e1c6 Fix the sanity check by pinning.
8891d8107 Merge pull request #519 from json-schema-org/ether/custom-dialect
5f5fccda3 test the format-assertion vocabulary with a custom metaschema
3fcee3868 Merge pull request #512 from json-schema-org/ether/formats-and-non-strings
b349b8797 test that format-assertions are valid with non-string types
8e5b2f10d fix needless inconsistencies in format tests between drafts
02d7cb59a Correct "ref with sibling id" tests
1649470ba More ipv6 tests to increase coverage
7334b4c7e Merge pull request #505 from ChALkeR/chalker/fix-unicode
0fb2d2787 Consolidate optional/unicode into optional/ecmascript-regex
4f8c6d7bf unevaluatedProperties: deep dynamic + refs
9103f3b6f $ref wit id does not test what it is indented to do
f300dd15f Add test "same $anchor with different base uri"
d128f9d7f Add test to check that $id resolved against nearest parent, not just immediate parent
72e31dd20 Merge pull request #515 from json-schema-org/ether/fix-mandatory-format-tests
0173a0835 Revert "by default, "format" only annotates, not validates"
66e813a90 Merge pull request #506 from json-schema-org/ether/formats-non-ascii
9430972bc fix unicode tests in accordance to pattern/patternProperties spec
git-subtree-dir: json
git-subtree-split: 54440eab4d50b80a62cc9f9c561e306cdbb19591
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It seems to have stopped running, even though I don't believe
anything related to it has changed, but it'll require some
diagnosis that I don't have time for at the minute to figure
out what precisely.
|
| |/
|/| |
|
|\ \
| | |
| | | |
Move python_requires to options for correct METADATA generation.
|
|/ / |
|
| |
| |
| |
| | |
Closes: #784
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
julian@Airm ●
We need a better public API for vocabularies, and this unfortunately
won't cut it.
For now this is dirty, but works to load all vocabularies (which
are just concatenated together).
The reason this is needed is because I don't see a PEP302-compliant
way to load a whole directory using the importlib.resources APIs
(which call directories 'packages') -- and doing so manually would
break importing jsonschema via a zip file, which is something
historically that users were doing.
|
| |
| |
| |
| |
| | |
Support for dynamicRef will come with a redesign of ref resolution,
but can't keep blocking the release.
|
|\ \
| | |
| | | |
Don't build universal wheels for Python 3-only
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
[pre-commit.ci] pre-commit autoupdate
|
|/ /
| |
| |
| |
| |
| |
| | |
updates:
- [github.com/pre-commit/pre-commit-hooks: v3.4.0 → v4.0.1](https://github.com/pre-commit/pre-commit-hooks/compare/v3.4.0...v4.0.1)
- https://github.com/timothycrosley/isort → https://github.com/PyCQA/isort
- [github.com/PyCQA/isort: 5.7.0 → 5.9.3](https://github.com/PyCQA/isort/compare/5.7.0...5.9.3)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Besides having confusing names, these expose mutable global state in
a way that makes maintenance hard.
Today, jsonschema.validators.validator_for(schema) can be used
to look up an appropriate Validator given an arbitrary schema.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These indeed can be improved, as mentioned in
https://github.com/Julian/jsonschema/pull/817#issuecomment-881550313
but it's a bit less clear exactly how yet -- rather than putting $ref
in the schema path, instead using relative_schema_path to only refer
to the schema post-$ref lookup is a bit more consistent with the current
norms, wherein what's in schema_path should be lookup-able via indexing.
But for now, they're distinguishable via .schema, which shows only the
$ref'ed schema for the second error.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A Validator should be thought of as encapsulating validation with a
single fixed schema.
Previously, iter_errors and is_valid allowed passing a second argument,
which was a different schema to use for one method call.
This was mostly for convenience, since the second argument is often
used during sub-validation whilst say, recursing.
The correct way to do so now is to say:
validator.evolve(schema=new_schema).iter_errors(...)
validator.evolve(schema=new_schema).is_valid(...)
instead, which is essentially equally convenient.
Closes: #522
|
| |
| |
| |
| |
| | |
This will soon be deprecated, and these tests don't care
about specifically doing things this way.
|
| |
| |
| |
| | |
Removes some testing redundancy as well.
|
| |
| |
| |
| | |
Also switch to using attrs to instantiate / repr them.
|