json updates to 6 files in public/schemas

[nsimon]

1. Updated $schema":"http://json-schema.org/draft-04/schema#" to
   "$schema":"http://json-schema.org/draft-06/schema#"

2. Changed types on all min/max field values from string to integer.

Original draft-04 was throwing an error in my linux Firefox (v58.0.2) dev console:
"Error: no schema with key or ref".

I changed the source json $schema values to use draft-06, and then saw a more useful error message. Can't recall the exact error syntax, but it referred to all of the min/max fields being invalid string types, which I then fixed to be integers. That solved the issue.

I suspect the original draft-04 schemas were working in other os/browser environments, due to a less stringent JVM running in those browsers. Perhaps the linux Firefox JVM was less forgiving?

Neil

[nsimon]

More (possibly helpful) info.

"Error: no schema with key or ref" -- was thrown when I clicked the Continue button to add an item.

[ryana]

Hey @wanderingstan just FYI I helped Neil put this PR together. I'm not sure on the content of this PR. It seems right on the surface but I don't know enough about the JSON schema stuff just yet to be sure. I mostly just wanted to help Neil to go through the process of submitting a PR. Let us both know what you think when you get around to it.

[tyleryasaka]

To shed some more light on why this error was happening, FWIW:

If you look at our package-lock.json, you'll see that we have a couple packages that have the ajv package as a dependency. ethereumjs-testrpc has version 5.5.2 as a dependency, and react-jsonschema-form and fsevents have version 4.11.8 as a dependency. I think due to this ambiguity different versions were getting loaded in different environments (which is why only some people had this issue). If version 5 was loaded, this causes an error (see the note in ajv's readme). That note has instructions to support draft-04 schemas, but unfortunately there's no way to do that with our usage through react-jsonschema-form at the moment (see this PR).

All that to say, this fix looks good. 😃

[nsimon]

Thanks. and great explanation Tyler! I also saw the ajv version discrepancies (in package-lock.json). It stood out to me, but I didn't really know what to make of it.

[wanderingstan]

Thanks for this, @nsimon !

[nsimon]

Hey @wanderingstan glad I could help!