pandastrike/jsck issues and pull requests

#106 - Support for newer drafts?

Issue - State: open - Opened by handrews over 6 years ago - 2 comments

#105 - pretty print errors

Issue - State: open - Opened by dyoder almost 7 years ago - 2 comments

#104 - Handle single schema transparently

Issue - State: open - Opened by dyoder over 7 years ago

#103 - Error thrown during validation if schema contains an `id`

Issue - State: open - Opened by jasonkarns over 7 years ago - 9 comments

#102 - schema-inspector is missing

Issue - State: open - Opened by Nonemoticoner over 8 years ago

#101 - Deviation from draft4 spec - additionalItems / additionalProperties is object or boolean, not object or false.

Issue - State: open - Opened by MrTrick over 8 years ago

#100 - don't crash if a $ref to an empty schema is found

Pull Request - State: closed - Opened by cxreg almost 9 years ago - 1 comment

#99 - allow draft4 validator to provide specific errors when anyOf or oneOf fail

Pull Request - State: closed - Opened by cxreg almost 9 years ago - 14 comments

#98 - Speculative error reporting for anyOf / oneOf

Issue - State: open - Opened by cxreg about 9 years ago - 5 comments

#97 - Regression on ref to empty schema crashes JSCK

Issue - State: open - Opened by cxreg about 9 years ago - 8 comments

#96 - Feature request: line numbers on error

Issue - State: closed - Opened by braco about 9 years ago - 2 comments

#95 - Use "plain" JS for README examples

Issue - State: open - Opened by aaronshaf about 9 years ago - 1 comment

#94 - TypeError with Nested Schema, Required, and Nulls

Issue - State: closed - Opened by SciencePiggy about 9 years ago - 11 comments

#93 - updated benchmarks, changed all validators versions to "latest"

Pull Request - State: closed - Opened by epoberezkin about 9 years ago - 1 comment

#92 - Added ajv to benchmarks, added all benchmarks to readme

Pull Request - State: closed - Opened by epoberezkin over 9 years ago - 2 comments

#91 - npm update

Issue - State: closed - Opened by SciencePiggy over 9 years ago - 3 comments

#90 - benchmark documents with errors

Issue - State: closed - Opened by gilesbowkett over 9 years ago - 1 comment

#89 - Is the browser a supported platform?

Issue - State: closed - Opened by tvjg over 9 years ago - 5 comments

#88 - Add JSEN to the benchmark

Pull Request - State: closed - Opened by bugventure over 9 years ago - 2 comments

#87 - Added missing `cd`

Pull Request - State: closed - Opened by analog-nico over 9 years ago - 1 comment

#86 - undefined properties should not cause validation to fail

Pull Request - State: closed - Opened by cxreg over 9 years ago - 1 comment

#85 - Make JSCK client-friendly by removing dynamic require statements

Pull Request - State: closed - Opened by jackwanders over 9 years ago - 3 comments

#84 - Explicitly allowing undefined

Issue - State: closed - Opened by moll over 9 years ago - 29 comments

#83 - Fix broken link

Pull Request - State: closed - Opened by markhuge over 9 years ago - 1 comment

#82 - Add themis to benchmarks

Pull Request - State: closed - Opened by atrniv almost 10 years ago - 3 comments

#81 - check into themis

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 16 comments

#80 - update readme/docs

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 1 comment

#79 - Document the task system.

Issue - State: open - Opened by automatthew almost 10 years ago
Labels: docs

#78 - Fix problem with missing file in benchmarks

Pull Request - State: closed - Opened by ebdrup almost 10 years ago - 14 comments

#77 - Update readme and benchmarks to include is-my-json-valid results

Pull Request - State: closed - Opened by ebdrup almost 10 years ago - 1 comment

#76 - Include mc-schema in bechmarks, It's faster

Issue - State: closed - Opened by mctep almost 10 years ago - 9 comments

#75 - no fat arrows

Pull Request - State: closed - Opened by dyoder almost 10 years ago - 6 comments

#74 - add is-my-json-valid 2.0.2 to the benchmark

Pull Request - State: closed - Opened by mafintosh almost 10 years ago - 14 comments

#73 - Fixes #72 add is-my-json-valid to benchmarks

Pull Request - State: closed - Opened by ebdrup almost 10 years ago - 4 comments

#72 - You should include the module is-my-json-valid by mafintosh, It's the fastest

Issue - State: closed - Opened by ebdrup almost 10 years ago - 21 comments

#71 - have benchmarks optionally output a CSV

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 8 comments

#70 - Schema compilation fails when a property is named "id"

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment
Labels: bug

#69 - Concern when benchmarking tv4 against invalid docs

Issue - State: closed - Opened by automatthew almost 10 years ago

#68 - Error reports aren't useful when a $ref is involved.

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment
Labels: wontfix

#67 - write up and report json-schema bug

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 1 comment

#66 - refactor benchmarking code

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 1 comment

#65 - double-check utc-millisec and URL regex in example schemas

Issue - State: closed - Opened by gilesbowkett almost 10 years ago

#64 - z-schema benchmarks (draft 4 only)

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago - 2 comments

#63 - json-gate benchmarks

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago

#62 - Replace rake tasks with something native.

Issue - State: closed - Opened by automatthew almost 10 years ago

#61 - jayschema benchmarks

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago

#60 - "required" is not a reserved word

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 1 comment

#59 - Benchmark draft subdirs

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago

#58 - tv4 benchmarks

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago

#57 - simple tv4 benchmarks

Pull Request - State: closed - Opened by gilesbowkett almost 10 years ago

#56 - reference resolution in compile_references ignores some draft4 attributes

Issue - State: closed - Opened by automatthew almost 10 years ago
Labels: bug

#55 - Review "invalid" tests for missing attributes.

Issue - State: open - Opened by automatthew almost 10 years ago
Labels: testing

#54 - Option to disable "format" validation.

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment
Labels: enhancement

#53 - Create separate dirs in benchmark/ for draft3 and draft4

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment

#52 - Verify that benchmarked libs aren't failing

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment

#51 - convenience method for checking whether a schema is malformed

Issue - State: open - Opened by automatthew almost 10 years ago - 1 comment
Labels: enhancement

#50 - test possibility of malformed schemas

Issue - State: closed - Opened by gilesbowkett almost 10 years ago - 2 comments

#49 - Update advanced usage examples for draft4

Issue - State: closed - Opened by automatthew almost 10 years ago
Labels: docs

#48 - Document how to add new schemas to benchmarks.

Issue - State: closed - Opened by automatthew almost 10 years ago
Labels: docs

#47 - Look for untested cases in draft4 support, add tests to suite.

Issue - State: closed - Opened by automatthew almost 10 years ago
Labels: coverage

#46 - Benchmark for a schema that uses as many attributes as possible.

Issue - State: closed - Opened by automatthew almost 10 years ago - 1 comment

#45 - test runner should use CLI flags for specifying attribute and individual test

Issue - State: open - Opened by automatthew almost 10 years ago - 2 comments
Labels: testing

#44 - Use Travis for CI?

Issue - State: closed - Opened by automatthew about 10 years ago - 1 comment

#43 - Add case to draft4 "type" test to outlaw removed behavior

Issue - State: closed - Opened by automatthew about 10 years ago

#42 - JSCK does not support minLength and maxLength tests of unicode surrogate pairs

Issue - State: closed - Opened by automatthew about 10 years ago - 3 comments
Labels: coverage