creek-service/json-schema-validation-comparison

Issues

• Format assertions should be enabled for `optional/ecmascript-regex.json`

  #190 opened 2 months ago by justin-tay
  5

• Some more libraries

  #215 opened 3 months ago by Vampire
  0

• Adjust format validation rules when running 2020-12 specs

  #79 opened a year ago by erosb
  6

• Include information about if library can perform streaming validation

  #73 opened a year ago by djarnis73
  1

• Split spec compliance chart to required & optional

  #69 opened a year ago by harrel56
  2

• Report full set of dependencies each implementation brings in

  #56 opened a year ago by big-andy-coates
  0

• Remove snow from performance graphs as its skewing the graphs

  #70 opened a year ago by big-andy-coates
  0

• Include version info in results

  #47 opened a year ago by big-andy-coates
  0

• Utilise `Implementations.all()` to programatically detect all implementations to unit test.

  #61 opened a year ago by big-andy-coates
  0

• Report supported Java versions.

  #57 opened a year ago by big-andy-coates
  0

• Include some more infos for each implementation

  #51 opened a year ago by harrel56
  2

• Report each implementations raw jar size.

  #55 opened a year ago by big-andy-coates
  0

• Add serde benchmarks for all impls that support Draft 2020-12

  #59 opened a year ago by big-andy-coates
  0

• Add a conclusions page to the microsite.

  #60 opened a year ago by big-andy-coates
  0

• Data driven performance results

  #53 opened a year ago by big-andy-coates
  0

• Data-driven functional results

  #52 opened a year ago by big-andy-coates
  0

• Make table of tested implementations data driven.

  #45 opened a year ago by big-andy-coates
  0

• Make it easier to add a new implementation

  #43 opened a year ago by big-andy-coates
  5