PHP User Experience of using JSON-Schema #388
Comments
|
That's not a bad idea. Thanks for the suggestion - I will implement this :-). |
|
👍 I like that idea a lot. All my schemas are simple PHP arrays, and it's always vaguely bothered me that I have to convert them to objects. |
erayd
added a commit
to erayd/json-schema
that referenced
this issue
Mar 16, 2017
|
Implemented in #389. Will backport to 5.2.0 once merged. |
erayd
added a commit
to erayd/json-schema
that referenced
this issue
Mar 17, 2017
erayd
added a commit
to erayd/json-schema
that referenced
this issue
Mar 19, 2017
bighappyface
pushed a commit
that referenced
this issue
Mar 21, 2017
* Allow the schema to be an associative array Implements #388. * Use json_decode(json_encode()) for array -> object cast * Skip exception check on PHP versions < 5.5.0 * Skip test on HHVM, as it's happy to encode resources
erayd
added a commit
to erayd/json-schema
that referenced
this issue
Mar 21, 2017
* Allow the schema to be an associative array Implements jsonrainbow#388. * Use json_decode(json_encode()) for array -> object cast * Skip exception check on PHP versions < 5.5.0 * Skip test on HHVM, as it's happy to encode resources
bighappyface
pushed a commit
that referenced
this issue
Mar 22, 2017
* Add URI translation for retrieval & add local copies of spec schema * Add use line for InvalidArgumentException & adjust scope (#372) Fixes issue #371 * add quiet option (#382) * add quiet option * use verbose instead of quiet * add quiet option * always output dump-schema * always output dump-schema-url * fix typo and ws * [BUGFIX] Add provided schema under a dummy / internal URI (fixes #376) (#378) * Add provided schema under a dummy / internal URI (fixes #376) In order to resolve internal $ref references within a user-provided schema, SchemaStorage needs to know about the schema. As user-supplied schemas do not have an associated URI, use a dummy / internal one instead. * Remove dangling use * Change URI to class constant on SchemaStorage * Add option to disable validation of "format" constraint (#383) * Add more unit tests (#366) * Add test coverage for coercion API * Complete test coverage for SchemaStorage * Add test coverage for ObjectIterator * Add exception test for JsonPointer * MabeEnum\Enum appears to use singletons - add testing const * Don't check this line for coverage mbstring is on all test platforms, so this line will never be reached. * Add test for TypeConstraint::validateTypeNameWording() * Add test for exception on TypeConstraint::validateType() * PHPunit doesn't like an explanation with its @codeCoverageIgnore... * Add various tests for UriRetriever * Add tests for FileGetContents * Add tests for JsonSchema\Uri\Retrievers\Curl * Add missing bad-syntax test file * Restrict ignore to the exception line only * Fix exception scope * Allow the schema to be an associative array (#389) * Allow the schema to be an associative array Implements #388. * Use json_decode(json_encode()) for array -> object cast * Skip exception check on PHP versions < 5.5.0 * Skip test on HHVM, as it's happy to encode resources * Enable FILTER_FLAG_EMAIL_UNICODE for email format if present (#398) * Don't throw exceptions until after checking anyOf / oneOf (#394) Fixes #393 * Fix infinite recursion on some schemas when setting defaults (#359) (#365) * Don't try to fetch files that don't exist Throws an exception when the ref can't be resolved to a useful file URI, rather than waiting for something further down the line to fail after the fact. * Refactor defaults code to use LooseTypeCheck where appropriate * Test for not treating non-containers like arrays * Update comments * Rename variable for clarity * Add CHECK_MODE_ONLY_REQUIRED_DEFAULTS If CHECK_MODE_ONLY_REQUIRED_DEFAULTS is set, then only apply defaults if they are marked as required. * Workaround for $this scope issue on PHP-5.3 * Fix infinite recursion via $ref when applying defaults * Add missing second test for array case * Add test for setting a default value for null * Also fix infinite recursion via $ref for array defaults * Move nested closure into separate method * $parentSchema will always be set when $name is, so don't check it * Handle nulls properly - fixes issue #377 * Add option to also validate the schema (#357) * Remove stale files from #357 (obviated by #362) (#400) * Stop #386 sneaking in alongside another PR backport
erayd
added a commit
to erayd/json-schema
that referenced
this issue
Mar 22, 2017
* Allow the schema to be an associative array Implements jsonrainbow#388. * Use json_decode(json_encode()) for array -> object cast * Skip exception check on PHP versions < 5.5.0 * Skip test on HHVM, as it's happy to encode resources
|
@bighappyface Can this issue be closed? The fix is merged in both 6.0.0-dev and 5.2.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently for an inline schema, it must be all objects. Since PHP mostly associative arrays to represent objects in Javascript, why not allow associative arrays to be valid schemas?
I always use the
Constraint::CHECK_MODE_TYPE_CASTright now, and this is great since I always runjson_decode(..., true). But I find it very verbose to have to type coerce all my validator schemas as(object) [...].The text was updated successfully, but these errors were encountered: