Old code

• Checksall validators.
• Picks thefirst one that validates, but can switch later if a better match is found.
• Bug: sometimes throws away the "best fit" when a validator fails.

New PR code

• Stops checking as soon as it finds thefirst validator that passes.
• Fixes the bug (no longer discards best fit on failure).
• But now itwon’t find a better match later — only the first valid one counts.

Conclusion

• ✅ If you want“first valid wins”, the PR is fine (but the title is misleading).
• ⚠️ If you want“best match”, the PR breaks that and should be adjusted.

@zeze0556 It looks to me that what you want is already in the old version

For the following schema definition:

{"type":"object","properties":{"foo":{"anyOf":[{"$ref":"#/definitions/A"},{"$ref":"#/definitions/B"}]}},"definitions":{"A":{"type":"object","properties":{"type":{"enum":["A"],"type":"string"},"referenced":{"$ref":"#/definitions/ReferencedObject"}},"required":["type"]},"B":{"type":"object","properties":{"type":{"enum":["B"],"type":"string"},"referenced":{"properties":{"foo":{"type":"string"},"bar":{"type":"string"}},"type":"object"},"addon":{//<== new addon with default"type":"string","default":"addon"}},"required":["type","addon"//<== make it required]},"ReferencedObject":{"properties":{"foo":{"type":"string"},"bar":{"type":"string"}},"type":"object"}}}

For the definition of legacy data:

{"foo": {"type":"B","referenced": {"foo":"","bar":""            }          }}

Versions >= 2.6.0 getValue() will return:

{"foo": {"type":"A","referenced": {"foo":"","bar":""        }    }}

Versions < 2.6.0 getValue() will return:

{"foo": {"type":"B","referenced": {"foo":"","bar":""        },"addon":"addon"    }}

This patch will not break the legacy data and will update it to the new data structure.

This is relatively friendly for automatic data updates.

I think there should be an editor option to enable this feature.

I tested in my local copybut idid not seea difference with the provided schema.
Could you list your steps list to reproduce your case, please?

var editor = JSONEditor(dom,{      schema: schema, //use comment schema      startval: {          "foo": {            "type": "B",            "referenced": {              "foo": "",              "bar": ""            }          }},      keep_oneof_values:false    });console.log('value=', editor.getValue());

If the version is >= 2.6.0, it will automatically match "#/definitions/A".
If the version is < 2.6.0, it will match the correct schema: "#/definitions/B".
In this case, the correct match should be "#/definitions/B".

json-editor is at version 2.15.2 at the moment.
Using the changes in the Pull Request does not change the json output in my local copy 😕