Michael Cohen

@rubenmoya Any input on the progress of this would be greatly appreciated. We currently use react-tool v1.3.4 and we'd like to upgrade our projects to use react v16.

@graydonpleasants See https://github.com/react-toolbox/react-toolbox/pull/1814#issuecomment-369008874

@theskillwithin Agree, however, one major blocker is that (currently) only @javivelasco is able to publish new packages to npm 😕

Hi 👋 -- I just came across this exact problem. I think the fundamental problem lies with the v2020-12 spec. > We are open to all suggestions on the design...

@stevehu Since my suggestion focuses on changing the type and would be considered a breaking schema change, seems like it'd be worth raising as a discussion here https://github.com/json-schema-org/community/discussions.

> At this moment, we don't know which way to go as it is not clear road map of schema specification team. @stevehu Thanks for the additional details. Good to...

Going back over the JSON Schema 2020-12 release notes, the following is [stated](https://json-schema.org/draft/2020-12/release-notes.html#changes-to-items-and-additionalitems): > Although the meaning of items has changed, the syntax for defining arrays remains the same. Only...

@stevehu Yep. I've started to dig into the code you referenced. Getting myself oriented with how it works.

@bmaizel Apologies for my slowness. I was digging into the code. First part was just orienting myself to how the [PrefixItemvalidator](https://github.com/networknt/json-schema-validator/blob/master/src/main/java/com/networknt/schema/PrefixItemsValidator.java) works within the broader context of JsonSchema and JsonMetaSchema...

After familiarizing myself with the code, a couple of observations... To get `items` field to work with the 2020-12 spec, you can update `ValidatorTypeCode.ITEMS` version code to be `VersionCode.AllVersions`. (The...