Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for optional strict validation of types #391

Closed
adi69 opened this issue Feb 9, 2018 · 1 comment
Closed

Add support for optional strict validation of types #391

adi69 opened this issue Feb 9, 2018 · 1 comment

Comments

@adi69
Copy link

adi69 commented Feb 9, 2018

One should have the freedom to check for types inside strings.
For instance, given the following schema

    {
        "schema": {
            "id": "schema_id",
            "properties": {
                "age": {
                    "type": "integer",
                    "description": "",
                }
            }
        }
    }

above schema should validate true for following data when strict validation is False

{ "age": "23" }

Why? It'll be helpful in API validation of query in GET requests and headers.

@Julian
Copy link
Member

Julian commented Feb 9, 2018

This sounds like the opposite of "strict" :)

It's possible already though to do now that we've got fully extendable type checkers. Haven't tidied up enough to do a release just yet, but if you give HEAD a try you'd be able to do this.

Feedback welcome.

@adi69 adi69 closed this as completed Feb 13, 2018
Julian added a commit that referenced this issue Apr 13, 2021
15ec577 Merge pull request #471 from json-schema-org/ether/id-anchor-in-enum
9f97865 test for confusing not-identifiers in enums
0f7ecd4 Merge pull request #475 from marksparkza/marksparkza-patch-1
783d22a Add jschon
fc68499 Merge pull request #472 from json-schema-org/ether/unevaluatedProperties_uncles
ed4cf5f more test cases for unevaluatedItems, unevaluatedProperties
d0d814d Merge pull request #469 from json-schema-org/ether/ipv4-vulnerability
7ca5f36 reject ipv4 strings with an octet with a leading zero
8e1e1c1 fix spelling error in test descriptions
77f1d10 Merge pull request #462 from jdesrosiers/dynamic-ref-tests
72a32fe Merge pull request #468 from json-schema-org/ether/combine-test-cases
0c48ffb Merge pull request #453 from notEthan/float-overflow-d4-int
76a4ba0 these test cases can be combined since the schemas are the same
cd73775 Merge pull request #464 from json-schema-org/ether/format-by-default-always-validates
043dc63 by default, "format" only annotates, not validates
3c45b81 Merge pull request #460 from amosonn/remove-remotes-from-script
b09e48d Fix $ref with siblings in pre-2019-09 tests
ff9f22e Add tests for $dynamicRef/$dynamicAnchor
0faaf09 Fix refs to Draft 2019-09 schema to be refs to 2020-12
ebbcbc8 Use flask to server remotes directly
bb98b03 Remove remotes from bin/jsonschema_suite
fcae732 Merge pull request #455 from jdesrosiers/bootstrap-202012
e002409 Update tests for 2020-12
405b3fb Copy 2019-09 tests to bootstrap 2020-12 tests
1636a22 draft4 float-overflow instance may be considered not an integer
8daea3f Merge pull request #451 from json-schema-org/ether/more-relative-json-pointer
69fe40f some more relative-json-pointer tests
6505944 Merge pull request #450 from json-schema-org/ether/recursiveRef-dynamic-path
afd0cd3 Move content* keyword tests to non-optional
e2b2a4b Change all content* keyword tests to always validate
8999eae $recursiveRef example demonstrating dynamic nature of the resolution scope
f47003f fix duplicate test description
bcf1dc8 Merge pull request #391 from ether/recursiveRef (rebased, squashed)
3d88f34 test $recursiveRef + $recursiveAnchor
3b79a45 Merge pull request #418 from ChALkeR/chalker/contentSchema
29f609b Add tests for contentSchema

git-subtree-dir: json
git-subtree-split: 15ec577f5ddee0115319f4e7f856cd57567a9c78
Julian added a commit that referenced this issue Jun 16, 2022
d40b3e62f Fix two remaining future-keywords tests in draft 4.
c23c720a2 Merge branch 'ether/unrecognized-keywords'
ea68a4ffd Move the future keywords tests to optional.
900695b74 squash: add $schema keyword to be clear that strict conformance is requested
acfd00c6f squash: contains does not exist in draft4
f506651a6 squash: fix minContains
b666c2023 sq - add $dynamic*, prefixItems to drafts 4,6,7 as well and fix keyword name
d14242e6e squash: fix test names
f1efe00df squash: $defs - definitions
c295358e7 squash: remove tests of $anchor and $ref
9defa7720 squash: add prefixItems: another new 2020-0X keyword
ebb359df5 squash: add $recursiveRef tests from #391
90bd7fb20 squash - fix 2019-09 future-keywords
e8e64efa1 very basic test of $dynamicRef
6c0272091 rename files to future-keywords.json
cb064e960 some tests for keywords added in later drafts

git-subtree-dir: json
git-subtree-split: d40b3e62f3156c576d7b8fad1afc3615c885ac67
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants