| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This probably worked before, but I typoed the classifiers ha.
|
|
|
|
| |
Closes: #1085
|
|
|
|
|
|
| |
Revert "Add the new JSON and JSON Schema classifiers, hooray!"
This reverts commit 9bd72530f100c16bfe3e6b0b35abe7de70087ef9.
|
| |
|
|\
| |
| |
| |
| | |
* commit 'b695cd7efa3e40fc41721792b4a692436b9eca39':
Squashed 'json/' changes from 0788c226a..6afa9b38d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
6afa9b38d Merge pull request #664 from santhosh-tekuri/empty-tokens
e4bceb1ad Bump the python-jsonschema version used for the sanity check.
8025fc0d5 Merge pull request #128 from iainbeeston/foundations-of-json-schema-paper
cf7677078 Make all root $ids absolute URIs
07fd389a3 Added test cases from Foundations of JSON Schema research paper
1008edcee ref: test empty tokens in json-pointer
9beb3cfba Merge pull request #627 from json-schema-org/ether/output-readme-fixes
f2b0490ba minor edit to trigger gh action
c305ce54f Merge pull request #669 from hauner/typo
5e2845c1e Merge pull request #668 from hauner/if-without-then-else-creates-annotations
2f1df2293 typo
c1fae0022 test unevaluated* can see annotations from if without then/else
987a4c8fc Merge pull request #666 from json-schema-org/gregsdennis/file-refs
90b2a58ce fix *nix uris
68d18c6ac rename tests to fix sanity check
e9166bcbe fix indentation
1d1ec749a add file-id ref tests
fb60ed17c Merge pull request #663 from json-schema-org/ether/restore-format-tests
f32cd8b80 Revert "Revert "by default, "format" only annotates, not validates""
47958f82d Merge pull request #654 from santhosh-tekuri/output-escape
5262997e1 Merge pull request #661 from santhosh-tekuri/2019-output
ce2c16573 output-tests: correct 2019 output-schema.json
c9d943856 output: ensure ~ and / are escaped in json-pointer
f6b2324bf minor spelling and markdown formatting fixes; `valid` has also been removed from the tests
git-subtree-dir: json
git-subtree-split: 6afa9b38d84d45550ec703123eb4e8ec67a8ae75
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changing this without deprecation is backwards incompatible, so we
re-introduce a warning.
This only applies if you have not configured neither a Registry nor a legacy
RefResolver. Both of the former 2 cases already have 'correct' behavior (the
former will not automatically retrieve references and is not backwards
incompatible as it is a new API, and the latter will do so but is already
fully deprecated by this release).
Cloess: #1089
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new referencing behavior is more correct (which is why it exists),
but also means that even though `RefResolver` was/is untouched, it can
be called now with more subschemas than previously, and in some cases
that tickles this code to blow up (see the closed issue for a specific
example).
We simply now ignore non-strs, as doing so is no more wrong than this
code used to be.
Closes: #1085
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though RefResolutionError is deprecated (and already raises a
suitable warning), this should make some additional code warn rather
than blow up (i.e. if someone is catching RefResolutionError, that code
should continue to work though it will raise a warning).
Users can transition to non-deprecated APIs by directly catching
referencing.exceptions.Unresolvable.
Closes: #1069
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
ikonst/2023-03-27-unevaluatedProperties-do-not-validate
Don't evaluate properties twice on behalf of `unevaluatedProperties` validation
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | | |
* commit 'c8c0bdd52999e4e1a6a38ceca814d0943f3e7962':
Squashed 'json/' changes from 19947eaa1..0788c226a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
0788c226a Merge pull request #659 from jvtm/python311-date-iso8601-values
4248f3c73 test: cover ISO8601 date values accepted by Python 3.11 datetime module
git-subtree-dir: json
git-subtree-split: 0788c226aa30f5e8fa862f4aa80e59a0f5186597
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
jvtm/python311-date-fromisoformat-allows-extra-formats
fix: Python 3.11 date.fromisoformat() allows extra formats
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Python 3.11 and later allow additional ISO8601 formats in `datetime` module
ISO8601 parsing. These formats are not RFC3339 section 5.6 compliant.
Especially `datetime.date.fromisoformat()` now allows strings like:
* `20230328` (2023-03-28)
* `2022W527` (2023-01-01)
* `2023-W01` (2023-01-02)
* `2023-W13-2` (2023-03-28)
Fix by doing a regular expression check before passing the value to `datetime`
module. This made the original `.isascii()` check unnecessary.
See:
* https://docs.python.org/3/whatsnew/3.11.html#datetime
* https://github.com/python/cpython/commit/1303f8c927
* https://docs.python.org/3.11/library/datetime.html#datetime.date.fromisoformat
* https://www.rfc-editor.org/rfc/rfc3339#section-5.6
Tests covering the invalid values to be sent to json-schema-org/JSON-Schema-Test-Suite
Fixes #1056.
|
| | |
|
| | |
|
| |
| |
| |
| | |
(This could previously be None incorrectly).
|
| |
| |
| |
| |
| | |
This should re-enable validating from a thread other than the one that
originall imported jsonschema.
|
| | |
|
|\ \
| | |
| | | |
documentation mistype fix
|
|/ /
| |
| | |
Draft202012Validator.validate instead of Draft20212Validator.validate
|
| | |
|
| |
| |
| |
| |
| |
| | |
(Of course mostly for laziness -- but this now doesn't import the
exceptions module which doesn't appear in __all__, which was added for
E401 style lints, which...)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
(We no longer support it.)
|
| | |
|
| |
| |
| |
| | |
This is specified behavior, see json-schema-org/JSON-Schema-Test-Suite#643.
|
|\ \
| |/
| |
| |
| | |
* commit '5e16d74500493ef164b595daec622c4ba199644e':
Squashed 'json/' changes from f57d3e0cc..19947eaa1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
19947eaa1 test: unevaluatedProperties not affected by propertyNames
829270631 Check that large integers are multiples of small multipleOf
b59543f6e Merge pull request #647 from santhosh-tekuri/ref-start-slash
6e5d45d71 Merge pull request #646 from santhosh-tekuri/vocab-optional
0311dfda0 Merge pull request #651 from santhosh-tekuri/dynamicref-without-anchor
4503eeaf4 test: A $dynamicRef without anchor in fragment behaves identical to $ref
39af4c1ba test: $ref with absolute-path-reference
880c9933b test/vocabulary: ignore unrecognized optional vocabulary
fd80307ff Merge pull request #642 from santhosh-tekuri/time-2digit
a76ae650d Merge pull request #645 from json-schema-org/gregsdennis/add-vocab-tests-link
0e2b4eefd Merge pull request #643 from 0xSudarshan/main
2b78ccfc4 slight tweaking to wording
8716c4054 add link for vocab test suite to readme
c49ba5445 Fix an incorrect $schema identifier.
f0e5ce71e Added test for schema-items alongside "ignored" additionalItems
76dae88ab Merge pull request #640 from santhosh-tekuri/refRemote-anchor
cb82e237c Merge pull request #641 from json-schema-org/gregsdennis/unevaluated-not-draft-next
e4afd233a test/format: hour, min, sec must be two digits
7efd51313 fix unevaluatedProperties/not tests for draft-next
e39c6ea6a test/refRemote: anchor within remote ref
bf51b32fb Merge pull request #639 from json-schema-org/additionalItems-unevaluatedItems
52160b368 Add a test for 2019's interaction between additional/unevaluatedItems
69a09a339 Fixed tests for annotation collection inside not.
e4e1a220b Draft7 if/then/else ref tests need to be wrapped in an allOf.
f5bd2f6c3 Merge pull request #632 from json-schema-org/ether/annotations-inside-not
626b433e5 test that annations are collected inside a "not"
git-subtree-dir: json
git-subtree-split: 19947eaa1289168a49edd21bb7a8aa2098069ae0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
No idea why RTD seems to say:
Problem in your project's configuration. Invalid "build.tools.python":
.readthedocs.yml: Invalid configuration option: build.tools.python.
but let's hope it's some very very very specific hope that the file is called
.yaml now??
|
| |
| |
| |
| |
| |
| |
| |
| | |
Let's try combining advice from:
https://github.com/ImageMagick/ImageMagick/discussions/2033#discussioncomment-16094
https://github.com/readthedocs/readthedocs-docker-images/issues/155#issuecomment-1020655379
|
|\ \
| | |
| | | |
Maybe fix PDF builds (in ReadTheDocs).
|
|/ / |
|
| |
| |
| |
| | |
And elaborate even further on the ref change.
|
|\ \
| | |
| | | |
Replace `$ref` & `$dynamicRef` support / `RefResolver` with the new referencing library
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're not a general class, so we know what fields we need
ahead of time.
This seems to give ~15% speedup on Validator evolution, which
happens often as part of walking up and down schemas.
|
| | |
| | |
| | |
| | | |
Just use virtue in CI.
|
| | | |
|