Better logging for schema issues

Description

When using a large schema, it can be hard to find the specific schema issue from the log warnings. I recently received:

ignoring oneOf in dependencies because there isn’t exactly one subschema that is valid

I know there is an issue with the dependency schema for my form, but unfortunately I have several oneOf dependencies for several refs and I’m having trouble tracking down which one this refers to.

Steps to Reproduce

Create a form with an invalid dependency schema using oneOf

Expected behavior

I’d love to know which schema key this refers to in the console log that outputs when the form knows there is an issue. An external validator tool could be another solution.

Actual behavior

Generic warning in console:

ignoring oneOf in dependencies because there isn’t exactly one subschema that is valid

Version

1.2.1

[paintedbicycle]

@epicfaace Ok, you can reference https://github.com/mozilla-services/react-jsonschema-form/pull/1224

I tried to do a very small change here, but it might be beneficial to update other warnings around the lib. But I don’t know the code well enough.

[paintedbicycle]

Hi @epicfaace I’m sure there are other examples, but the exact one I came up against was this

Inside the the person ref, I simply changed:

              "properties": {
                "Do you have any pets?": {
                  "enum": [
                    "Yes: More than one"
                  ]
                },

to

              "properties": {
                "Do your have any pets?": {
                  "enum": [
                    "Yes: More than one"
                  ]
                },

Note the typo your in only one of the property definitions. So there is a mismatch.

If you open the console, you’ll see:

ignoring oneOf in dependencies because there isn’t exactly one subschema that is valid

Now, in my case, there were many of these anyOf properties. And I would have liked the warning message to simply tell me which one it was.

For example:

ignoring Do you have any pets? oneOf dependency because subschema is not valid